Support Sensitive values to node_encrypt::file #35
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
|
@binford2k I'm unclear on whether or not you get a notification when somebody makes a PR on your repos. Anyway, ping. |
This automatically unwraps Sensitive values in the node_encrypt function. If the Sensitive type isn't known (it was released in Puppet 4.6), this behaves as before.
|
Thanks kindly! I added a simple spec for it at 9461a75 |
|
Oh, thanks! I meant to do that, but I forgot. |
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.
This automatically unwraps
Sensitivevalues in thenode_encryptfunction.If the
Sensitivetype isn't known (it was released in Puppet 4.6), this behaves as before.I tried this on our 2019.0 server, and passing a
Sensitiveworked fine.