documentation: env option does not override environment settings #1733
Labels
state: duplicate
Duplicates another issue.
Comments
ssbarnea
added a commit
to ansible/vscode-ansible
that referenced
this issue
Aug 2, 2024
We do not want to accidentally use a virtualenv that was created by the developer as this is likely to be polluted. Related: go-task/task#1733
ssbarnea
added a commit
to ansible/vscode-ansible
that referenced
this issue
Aug 2, 2024
We do not want to accidentally use a virtualenv that was created by the developer as this is likely to be polluted. Related: go-task/task#1733
audgirka
pushed a commit
to ansible/vscode-ansible
that referenced
this issue
Aug 2, 2024
We do not want to accidentally use a virtualenv that was created by the developer as this is likely to be polluted. Related: go-task/task#1733
|
Duplicate of #1038. There is an experiment being released soon that will invert the default behaviour. Stay tuned |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure if this is by design or a bug, but clearly specifying "env:" values does not override already defined values existing in system environment before calling taskfile.
If this is expected, it should documented in a highlighted warning notice, so people would not be surprised about its behavior.
My expectation was that it would override because I could use the shell expansion will fallback mechanism if I would not want it to override environment. With current behavior, I have no way to force taskfile to define a specific environment value and ignore system one.
Effective example at https://github.com/ansible/vscode-ansible/blob/main/Taskfile.yml#L17-L18 -- where we cannot force our own
VIRTUAL_ENVvalue if the user defined his own in his shell.The text was updated successfully, but these errors were encountered: