Remove WindowsPrivacyAccessControl from module generation #3326
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR excludes the
deviceManagement_windowsPrivacyAccessControl
resource from being generated into the DeviceManagement module. This is necessary because it otherwise is "merged" with theGet-MgBetaDeviceManagementDeviceConfiguration
cmdlet, therefore resulting in a broken parameter set resolution.deviceManagement_windowsPrivacyAccessControl
is assigned theGet-MgBetaDeviceManagementDeviceConfiguration
command inMgCommandMetadata.json
. There, also the variantsAccess
,AccessExpanded
,AccessViaIdentity
andAccessViaIdentityExpanded
are defined. Having this definition there forces the merge of the defaultGet-MgBetaDeviceManagementDeviceConfiguration
cmdlet with this object, although this should have a dedicated cmdlet, or even better, simply be excluded because it doesn't serve a purpose in having it.Changes proposed in this pull request
deviceManagement_windowsPrivacyAccessControl
object from module generation.