powerful-football-8169401/07/2019, 2:04 PM
operations, but which are not config values stored in the stack but rather set and known by the release job on a per-release basis.
-c, --config stringArray Config to use during the update
and not on
pulumi config set ... && pulumi update
powerful-football-8169401/07/2019, 8:06 PM
just seems wrong, because this value is really not configuration that I'd like persisted in the stack. The value is by nature more of a parameter than a configuration value - if that makes sense?
pulumi config set
property of the Node.JS
import os print(os.environ["MYENVVAR"])
powerful-football-8169401/07/2019, 8:41 PM