Replies: 1 comment
-
Some experimentation shows that this is true, if the environment variables are created outside of .envrc then they are sticky, so I guess I can just be smart about what I put there, but it would be nice if direnv allow a passthrough, way easier to document as .envrc is such a great way to put dependencies in :-) |
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
-
OK, this is a complete noob question, I have some environment variables that take a long time to calculate (specifically they are retrieving secrets from 1Password).
I've been using "source_up_if_exists" and this is great to mirror all the environment variables from above, but this forces a long period of 1Password looking for things.
There must be some sort of stdlib thing that is a passthrough, but I can't find it. So for instance the idea is
If there is an OPENAI_API_KEY that is already in the environment then pass it down. The default behavior seems to be to shield the directory from all already exported variable, but another of the 93 exported variables I have before entering a direnv controlled directory, how does it determine which ones pass through and which don't?
It let's all kinds of variables through like CONDA_SHLVL, so is it just direnv declared environment variables that are removed everytime it sees a .envrc?
Beta Was this translation helpful? Give feedback.
All reactions