Env vars exported from shell scripts fail to render in subsequent templates #3783
Unanswered
bartsmykla
asked this question in
Troubleshooting
Replies: 1 comment
-
there is a TODO in the code which addresses why this happens—path gets loaded before tools. You can work around by having separate mise/src/config/config_file/mise_toml.rs Line 838 in 53c9144 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
Env vars exported from a shell script and loaded via
_.source
fail to render in subsequent env var templates. This behavior is inconsistent with how variables defined directly in the[env]
section work.This issue does not occur when the variable is defined directly in the
[env]
section.This is a followup for #3755
To Reproduce
.mise/env.sh
with the following content:mise
commandExpected behavior
The env var
{{ env.__GENERATE_TOOLS_DIR }}
should resolve to the value set in the shell script (foo
), and_.path
should render correctly.mise doctor
outputBeta Was this translation helpful? Give feedback.
All reactions