add support for replacing variable items value with environment variables #23
+82
−25
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
…replacements for other future files
… can potentially work for other files such as nomad job files in the future
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 introduces a new flag calledI have updated the README.md with links to http://dotenvx.com which even allows to check encrypted .env files in the source control. While there are other tools such as sops, git-secret, dotenvx is probably the most simple one for anyone to get started.--var-env-prefixwhich defaults toenv:. This allows us to replace variables with environment variables allowing us to store the secret in CI or have dynamic values without writing tools.[update]
Thinking more about this I updated the code to now use
--env-templatewhich uses<<$env(VARIABLE)>>prefix instead ofenv:. Right now I loop through the items in variables files, but in the future we could use the same template to expand to other files such as nomad jobs or even the entire variables file. Tried to use a template syntax that doesn't conflict with nomad variables. I'm using$env()to allow opportunities in the future to add support for other sources.