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
The ENV variable in this case is picked up from the command line or the value default_env is used otherwise, this is great. However, if VAR_X is set within .env file, then it is not picked up and the value will always be 123 due to the default; it would have to be set on the command line for it to be picked up.
Setting on the command line should take precedence, I think, but otherwise loading from a dotenv file next would be great.
I think there might be a chicken-and-egg situation such that the env vars need to be evaluated in order to select the correct dotenv file but maybe after loading dotenv the env vars defined in the env: section could be re-evaluated?
Thanks for a great tool, finding it really useful so far!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently, if you have:
The
ENV
variable in this case is picked up from the command line or the valuedefault_env
is used otherwise, this is great. However, ifVAR_X
is set within.env
file, then it is not picked up and the value will always be123
due to thedefault
; it would have to be set on the command line for it to be picked up.Setting on the command line should take precedence, I think, but otherwise loading from a dotenv file next would be great.
I think there might be a chicken-and-egg situation such that the env vars need to be evaluated in order to select the correct dotenv file but maybe after loading dotenv the env vars defined in the
env:
section could be re-evaluated?Thanks for a great tool, finding it really useful so far!
Beta Was this translation helpful? Give feedback.
All reactions