Make setting-level `env:` declaration a one-way injection into the plugin execution context
Follows from #3431 (closed): We want the env:
usage pattern to be fully unambiguous. The use case this exists for is so that plugins can receive injected environment variable values from Meltano.
- The user sets the setting value in any supported way.
- The plugin gets that setting value from the
env:
. - If an env var is already set by that name, its value will be replaced by the setting value.
For example: if the OS context has an env var set as DEBUG_MODE=1
but my plugin has a setting with env: DEBUG_MODE
and setting value of 0
, then the plugin when invoked will have DEBUG_MODE=0
, which is the value that the plugin is intended to receive by the Meltano user. Any other env vars from context will be ignored unless they are referenced under Any other env vars from context will be ignored when initializing the plugins settings unless they are referenced under value:
, env_aliases:
, or the config:
entry.value:
, env_aliases:
, or the config:
entry.