LGPO: Add support to apply registry settings directly to Registry.pol #62888
Conversation
This file contains hidden or 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
twangboy
force-pushed
the
fix_56013
branch
3 times, most recently
from
6a367b9 to
7d0b183
Compare
s0undt3ch
reviewed
Oct 17, 2022
twangboy
changed the title
twangboy
changed the title
garethgreenaway
approved these changes
Oct 18, 2022
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.
What does this PR do?
Creates a Module, State, and Util for working directly with the Registry.pol file on Windows
What issues does this PR fix or reference?
Fixes: #56013
Previous Behavior
You had to go through the LGPO module to set policy in Registry.pol
New Behavior
Now you can set registry policies directly with just the registry key/name
Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.
Commits signed with GPG?
Yes