Feature/Allow env file to override environment #42
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
Prior to this change, the environment always took precedence when there was a value specified in both the env file and the environment. This was not suitable to all use-cases (such as those in Kubernetes, where environment variables are commonly much less controlled and, so, much more vulnerable to malicious value injection). This change allows the developer to choose which takes precedence, the environment or the env file (with the current behaviour remaining the default).
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.
Prior to this change, the environment always took precedence when there
was a value specified in both the env file and the environment. This
was not suitable to all use-cases (such as those in Kubernetes, where
environment variables are commonly much less controlled and, so, much
more vulnerable to malicious value injection).
This change allows the developer to choose which takes precedence, the
environment or the env file (with the current behaviour remaining the
default).
Completes #40