-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Admin setting and group policy for configuration processor path argument #6119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -133,6 +133,15 @@ If you disable this setting, users will not be able to use the Windows Package M | |
| If you enable or do not configure this setting, users will be able to use the Windows Package Manager's MCP server. | ||
|
|
||
| If you disable this setting, users will not be able to to use the Windows Package Manager's MCP server.</string> | ||
| <string id="EnableWindowsPackageManagerConfigurationProcessorPath">Enable Windows Package Manager Configuration Processor Path</string> | ||
| <string id="EnableWindowsPackageManagerConfigurationProcessorPathExplanation"> | ||
| This policy controls whether users can specify a custom DSC processor path via the --processor-path argument in Windows Package Manager configuration commands. | ||
|
|
||
| If you enable this setting, users will be able to specify a custom DSC processor path in configuration commands. | ||
|
|
||
| If you do not configure this setting, users will be able to specify a custom DSC processor path in configuration commands after enabling the related administrator setting. | ||
|
|
||
| If you disable this setting, users will not be able to specify a custom DSC processor path in configuration commands.</string> | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I assume that not being able to set the custom processor path is the more secure option? Shouldn't that be the default if not configured?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, but maybe it should read "then the admin setting is considered, which is default disabled". This is similar to local manifest, as is the text here. Not Configured -> Admin setting is considered, defaults to disabled. |
||
| <string id="WindowsPackageManagerDefaultProxy">Set Windows Package Manager Default Proxy</string> | ||
| <string id="WindowsPackageManagerDefaultProxyExplanation">This policy controls the default proxy used by the Windows Package Manager. | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not a fan of this string. Maybe "Enable custom Configuration Processor Path for Windows Package Manager"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@denelon
Two questions:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Enable Windows Package Manager Configuration Processor Path
Enable Windows Package Manager Configuration Processor Override
Enable Windows Package Manager Custom Configuration Processor Path
Enable Custom Configuration Processor Path for Windows Package Manager
Enable Configuration Processor Override for Windows Package Manager