feat: Introduce support for supplying --env-file in compose
#2033
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
This commit introduces support to all compose subcommands (both in the local and cloud) for supplying an alternative environmental variables file (i.e. other than `.env`) via the flag `--env-file`. This increases compatibility with existing compose-based CLI tools like `docker`. Signed-off-by: Alexander Jung <[email protected]>
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.
This commit introduces support to all compose subcommands (both
in the local and cloud) for supplying an alternative environmental
variables file (i.e. other than
.env) via the flag--env-file.This increases compatibility with existing compose-based CLI tools
like
docker.Signed-off-by: Alexander Jung [email protected]
Prerequisite checklist
make fmton your commit series before opening this PR;Description of changes