You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#177 added a new !override YAML tag to cause an alias-level docker_args node to override the top-level docker_args, rather than the default behavior of concatenation.
Currently, an alias-level environment will be merged with the top-level environment (overriding if conflicting keys exist). This issue proposes allowing !override to be used in alias.environment also.
However, considering that environment is a dict/mapping, but docker_args is a string (which is shlexed into a list), environment kind of already naturally supports this operation. Since the environment dictionaries are merged (in order of command-line, top-level, alias), keys already override, allowing an alias to "kill-off" a top-level env var. It seems unlikely that you would want/need to kill-off all top-level env vars from an alias.
The text was updated successfully, but these errors were encountered:
This is a follow-up from #177 (comment).
#177 added a new
!override
YAML tag to cause an alias-leveldocker_args
node to override the top-leveldocker_args
, rather than the default behavior of concatenation.Currently, an alias-level
environment
will be merged with the top-levelenvironment
(overriding if conflicting keys exist). This issue proposes allowing!override
to be used inalias.environment
also.However, considering that
environment
is a dict/mapping, butdocker_args
is a string (which is shlexed into a list),environment
kind of already naturally supports this operation. Since the environment dictionaries are merged (in order of command-line, top-level, alias), keys already override, allowing an alias to "kill-off" a top-level env var. It seems unlikely that you would want/need to kill-off all top-level env vars from an alias.The text was updated successfully, but these errors were encountered: