Support for sensitive environment variables #111
Merged
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.
Pull Request (PR) description
The
environment
option does not support sensitive value. I would like to puthttp_proxy=http://user:[email protected]:3128
in an environment variable, but the content is displayed in cleartext in the log.This PR allow to define an
environment
content as sensitive as followed:same for
cron::job::multiple
There was validation in the
erb
template about theenvironment
variables, and funky.join(\n).split(\n)
but I think it is no longer necessary. The content is validated by puppet directly on the call tocron::job
. Is this behavior a remnant of old puppet when there was no types?I also removed the
environment
variable in thecron::job::multiple::jobs
array, as it was not defined in the olderb
, and kept the same behavior for theepp
.Feel free to raise concern if you think my assumptions were wrong
This Pull Request (PR) fixes the following issues