add: allow reading secrets from files #47
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.
What
Allow reading secrets from files.
Pass the path to the file containing the secret to the service by appending
_FILE
to the env var name which normally would contain the secret directly.If both env vars
SECRET
andSECRET_FILE
are set,SECRET
takes precedence.As the original way of supplying secrets is still supported, this is a backwards compatible change.
Why
Using the docker secrets feature results in files containing the secret being placed into the container filesystem.
References
VTI-300
Checklist