This repository has been archived by the owner on Oct 30, 2019. It is now read-only.
Allow specifying of facter variables during puppet apply. #40
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.
Sometimes you want to push additional variables to facter during
puppet apply. For instance, secrets should not be stored under version
control but are needed when the configuration is applied. In this instance
using passing the secret as a facter variable to puppet is a nice way
of having the configured machine have the secret but not include the secret
in your source code.
This patch lets you specify facter variables at parameters to
puppet docker build
that are in turn sent to thepuppet apply
call.