Parse files without using shell environment variables about shdotenv HOT 4 CLOSED

shdotenv is not designed to be a merge tool. However, env -i seems to be a good workaround.

In some environments, you may need to pass the PATH and some environment variables (e.g. SHDOTENV_AWK).

env -i PATH="$PATH" shdotenv --noexport --env .env.prod --env .env

Considering that all environment variables disappear, I think the addition of the -i (--ignore-environment) option is an acceptable feature.

from shdotenv.

For what purpose would you use this?

$ KEY1='blaaat' ./shdotenv --noexport --env test.env
KEY2='value2'

I don't want that. I want the result always to have both keys.

Which is the result you expect?

KEY1='value1'
KEY2='value2'

or

KEY1='blaaat'
KEY2='value2'

from shdotenv.

I expect this:

$ KEY1='blaaat' ./shdotenv --noexport --env test.env
KEY1='value1'
KEY2='value2'

So the command does not use existing env vars.

Right now, I have fixed it like this:

env -i shdotenv --noexport --env .env.prod --env .env

And that works fine as well.

My use case is that I want to use shdotenv to combine multiple .env files and let them overload into 1 consolidated file. That file is then put inside Kubernetes configuration. So reading from my current bash / env doesn't make sense, as the consolidated file will be executed on a different system anyway.

from shdotenv.

Done

from shdotenv.