resolve variables in .env file based on previously set variables#262
Merged
glours merged 1 commit intocompose-spec:masterfrom May 17, 2022
Merged
resolve variables in .env file based on previously set variables#262glours merged 1 commit intocompose-spec:masterfrom
glours merged 1 commit intocompose-spec:masterfrom
Conversation
Signed-off-by: Nicolas De Loof <[email protected]>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
variable substitution in
.envfile MUST not assume values from os.Env, but use previously registered environment variables (set either byWithOsEnvor by direct assignment toprojectOptions.Environment)variables MUST NOT override a previously defined variable, so that one can use:
FOO=BARset by os.envQIX=${FOO}set by .env fileFOO=...set by .env file does not override value set by os.envsee docker/compose#9442