You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.
Configuration: C:\Program Files\PowerShell\Modules\PSDscResources\2.12.0.0\DscResources\WindowsFeatureSet\WindowsFeatureSet.schema.psm1:39
Line |
39 | Configuration WindowsFeatureSet
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| The member 'Source' is not valid. Valid members are 'Credential', 'DependsOn', 'Ensure', 'IncludeAllSubFeature', 'LogPath', 'Name',
| 'PsDscRunAsCredential'.
InvalidOperation: C:\program files\powershell\7\Modules\PSDesiredStateConfiguration\PSDesiredStateConfiguration.psm1:3745
Line |
3745 | throw $ErrorRecord
| ~~~~~~~~~~~~~~~~~~
| Errors occurred while processing configuration 'InstallDotNet35'.
It looks like there is some conflicting documentation on whether that parameter even exists or not.
I hit this issue today. Looks like the WindowsFeatureSet proxies to the MSFT_WindowsFeature resource that lacks the Source property. This seems like a regression as previous functionality has been removed.
The PSDscResources module is intended to be a compatible replacement for the PSDesiredStateConfiguration module resources that come in-box with Windows. However, it does indeed look like the MSFT_WindowsFeature module is missing the Source property in the PSDscResources module.
I'm not sure how this feature has been missed out. An issue is also open on the community maintained version of this module for a similar feature: dsccommunity/xPSDesiredStateConfiguration#700
This should be an easy fix but I'll need to confirm with the team what the release schedule looks like.
Has this been addresses elsewhere in DSC modules? I have been searching with no luck. This is preventing moving away from older modules. Thanks for any insight
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugThe issue is a bug.help wantedThe issue is up for grabs for anyone in the community.
Failing to compile when using the Source member of WindowsFeatureSet
The result of attempting to compile is
Configuration: C:\Program Files\PowerShell\Modules\PSDscResources\2.12.0.0\DscResources\WindowsFeatureSet\WindowsFeatureSet.schema.psm1:39
Line |
39 | Configuration WindowsFeatureSet
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| The member 'Source' is not valid. Valid members are 'Credential', 'DependsOn', 'Ensure', 'IncludeAllSubFeature', 'LogPath', 'Name',
| 'PsDscRunAsCredential'.
InvalidOperation: C:\program files\powershell\7\Modules\PSDesiredStateConfiguration\PSDesiredStateConfiguration.psm1:3745
Line |
3745 | throw $ErrorRecord
| ~~~~~~~~~~~~~~~~~~
| Errors occurred while processing configuration 'InstallDotNet35'.
It looks like there is some conflicting documentation on whether that parameter even exists or not.
It's listed on the microsoft docs page https://docs.microsoft.com/en-us/powershell/scripting/dsc/reference/resources/windows/windowsfeaturesetresource?view=powershell-7#syntax
It's not listed on the GitHub page https://github.com/PowerShell/PSDscResources
It exists as a parameter in the file WindowsFeatureSet.schema.psm1, but isn't listed in the Comment-based Help for that function
The text was updated successfully, but these errors were encountered: