The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

--
how to translate this coded `resources` which is using `EnvVar`
<https://docs.dagster.io/guides/dagster/using-environment-variables-and-secrets#example-1-per-environment-configuration>
• to loading from YAML (so that the config file can be switched easily, w/o changing the code)
• but still with *envvar* expansion from `.env` file?
before I go with a custom approach like <https://python-dependency-injector.ets-labs.org/providers/configuration.html#configuration-envs-interpolation|dependency-injector support> for loading yaml-configs with envvars expansion

in yaml, you can specify it as:
```resources:
  resource_key_name:
    config:
      env: ENVIRONMENT_VARIABLE_NAME```
<https://docs.dagster.io/guides/dagster/using-environment-variables-and-secrets#in-yaml-or-config-dictionaries>

and then in your `.env` file, you’d specify as:
```ENVIRONMENT_VARIABLE_NAME=...```