I.e. we want the environment to be usable by env-config-run but not env-config so that the variables are prevented from being "sticky" in a CLI session.
My intended use case is to set this for environment variables needed to deploy to production. I don't want the vars to be sticky to avoid setting them in a CLI, forgetting that the prod env is active, and then later running deploy commands which should default to a dev environment but, because the prod env is accidentally active, deploying to prod instead.
I.e. we want the environment to be usable by
env-config-runbut notenv-configso that the variables are prevented from being "sticky" in a CLI session.My intended use case is to set this for environment variables needed to deploy to production. I don't want the vars to be sticky to avoid setting them in a CLI, forgetting that the prod env is active, and then later running deploy commands which should default to a dev environment but, because the prod env is accidentally active, deploying to prod instead.