Add support for Sensitive data in registry_value #316
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
- Updated REFERENCE.md to include Sensitive[String] in the data type options. - Enhanced registry_value provider to unwrap Sensitive values before processing. - Modified registry_value type to handle Sensitive data during value munging. - Updated value.pp documentation to demonstrate usage of Sensitive types. - Added unit tests to verify support for Sensitive data across different types.
|
|
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.
Summary
In the case, that you want to store a credential in registry, the credential is shown in clear text in log / puppetboard.
This change adds the support for Sensitive data in the registry module. So credentials are now shown in the log anymore.
Checklist
puppet apply)