There isn’t a single, definitive list of all configurable environment variables in the provided knowledge sources. The docs and Slack threads mention several patterns and specific examples, but also explicitly note that a comprehensive list is missing and was requested as a feature. [[config feedback](https://elementary-community.slack.com/archives/C02CTC89LAX/p1672946756861029?thread_ts=1672946756.861029&cid=C02CTC89LAX)] From what is documented: ### 1. CLI options via env vars Any

edr

CLI option can be set as an env var using:

EDR_<COMMAND>_<OPTION>=<VALUE>

[[CLI options](https://docs.elementary-data.com/oss/cli-commands#cli-options)] Example:

bash export EDR_REPORT_FILE_PATH="my_report.html" edr report # equivalent to: edr report --file-path "my_report.html"

Other examples from Slack: -

EDR_MONITOR_PROFILES_DIR

(equivalent to

edr monitor --profiles-dir ...

) [[profiles dir env](https://elementary-community.slack.com/archives/C02CTC89LAX/p1674673468533389?thread_ts=1674673468.533389&cid=C02CTC89LAX)] You can derive more by taking any flag from

edr <command> --help

/ the CLI docs and converting it to this pattern. ### 2. Orchestrator / job metadata env vars Elementary collects job metadata from env vars (and/or dbt vars): [[OSS collect jobs](https://docs.elementary-data.com/oss/guides/collect-job-data); [Cloud collect jobs](https://docs.elementary-data.com/cloud/guides/collect-job-data)] Generic env vars it reads: -

ORCHESTRATOR

-

JOB_NAME

-

JOB_ID

-

JOB_URL

-

JOB_RUN_ID

-

JOB_RUN_URL

Plus orchestrator‑specific ones (e.g. dbt Cloud, GitHub Actions) that Elementary uses to derive those fields. Older Slack threads also mention: -

DBT_JOB_ID

-

DBT_JOB_RUN_ID

-

DBT_JOB_NAME

[[dbt job envs](https://elementary-community.slack.com/archives/C02CTC89LAX/p1673374633074929?thread_ts=1673374633.074929&cid=C02CTC89LAX)] ### 3. dbt / profiles.yml env vars These are standard dbt

env_var()

usages inside

profiles.yml

and

dbt_project.yml

(Snowflake, Redshift, etc.), not Elementary‑specific, but they are used by Elementary’s profile, e.g.: [[profiles env vars](https://elementary-community.slack.com/archives/C02CTC89LAX/p1680524725868009?thread_ts=1680524725.868009&cid=C02CTC89LAX)]

yaml account: "{{ env_var('PROFILES_YML_SNOWFLAKE_ACCOUNT') }}" user: "{{ env_var('PROFILES_YML_SNOWFLAKE_USER') }}" password: "{{ env_var('PROFILES_YML_SNOWFLAKE_PASSWORD') }}" ... schema: "{{ env_var('PROFILES_YML_SNOWFLAKE_SCHEMA') ~ '_elementary' }}"

And similar patterns for Redshift, etc. --- Because the sources explicitly say a “definitive guide/page for configuration options and variables” is missing and was opened as a docs issue, there is no complete, authoritative list in the material you provided. [[config feedback](https://elementary-community.slack.com/archives/C02CTC89LAX/p1672946756861029?thread_ts=1672946756.861029&cid=C02CTC89LAX)] To discover more in your setup, you’ll need to: - Run

edr <command> --help

and convert flags to

EDR_<COMMAND>_<OPTION>

env vars. - Inspect the

collect-job-data

docs for orchestrator‑related env vars. - Use dbt’s own

env_var()

mechanism in

profiles.yml

/

dbt_project.yml

.