chore: add securityContext & remove allowPrerelease from winget config #6291
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
denelon
approved these changes
Mar 19, 2025
|
Thanks @mdanish-kh for helping improve "configuration as code" 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Prerequisites
Description
Microsoft.WinGet.DSC/WinGetPackageis GA now soallowPrerelease: truedirective can be removed. Also, installing NodeJS requires admin privileges, addedsecurityContext: elevatedfor that resource. What this directive does is that it will prompt for a single UAC at the start of the configuration and then launch two separated process - one elevated & one with current privileges. The resources that require elevation will be run in the elevated process