load secrets/configs from environment while parsing compose model #655
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
ndeloof
force-pushed
the
resolve_secrets_environment
branch
from
a35bd59 to
7c91287
Compare
Signed-off-by: Nicolas De Loof <[email protected]>
ndeloof
force-pushed
the
resolve_secrets_environment
branch
from
7c91287 to
91e457b
Compare
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.
As we load compose model with environment, resolve secrets and config values based on declared environment value.
This allows a nested model loading (using
include) to resolve such values based on configuredenv_file, not just top-level environment.when marshaling model to yaml/json resolved content is hidden if it was set by environment, to keep definition consistency
closes docker/compose#11952