Stable (2.10.5)2.10.52.10.42.10.32.10.22.10.12.10.02.9.32.9.22.9.12.9.02.8.42.8.32.8.22.8.12.8.02.7.32.7.22.7.12.7.02.6.32.6.22.6.12.6.02.5.32.5.22.5.12.5.02.4.32.4.22.4.12.4.02.3.42.3.32.3.22.3.12.3.02.2.52.2.42.2.32.2.22.2.12.2.02.1.42.1.32.1.22.1.12.1.02.0.32.0.22.0.12.0.01.10.151.10.141.10.131.10.121.10.111.10.101.10.91.10.81.10.71.10.61.10.51.10.41.10.31.10.21.10.1
Stable (2.10.5)2.10.52.10.42.10.32.10.22.10.12.10.02.9.32.9.22.9.12.9.02.8.42.8.32.8.22.8.12.8.02.7.32.7.22.7.12.7.02.6.32.6.22.6.12.6.02.5.32.5.22.5.12.5.02.4.32.4.22.4.12.4.02.3.42.3.32.3.22.3.12.3.02.2.52.2.42.2.32.2.22.2.12.2.02.1.42.1.32.1.22.1.12.1.02.0.32.0.22.0.12.0.01.10.151.10.141.10.131.10.121.10.111.10.101.10.91.10.81.10.71.10.61.10.51.10.41.10.31.10.21.10.1

Setting Configuration Options

The first time you run Airflow, it will create a file called airflow.cfg in your $AIRFLOW_HOME directory (~/airflow by default). This file contains Airflow’s configuration and you can edit it to change any of the settings. You can also set options with environment variables by using this format: $AIRFLOW__{SECTION}__{KEY} (note the double underscores).

For example, the metadata database connection string can either be set in airflow.cfg like this:

[core]
sql_alchemy_conn = my_conn_string
Copy to clipboard

or by creating a corresponding environment variable:

export AIRFLOW__CORE__SQL_ALCHEMY_CONN=my_conn_string
Copy to clipboard

You can also derive the connection string at run time by appending _cmd to the key like this:

[core]
sql_alchemy_conn_cmd = bash_command_to_run
Copy to clipboard

You can also derive the connection string at run time by appending _secret to the key like this:

[core]
sql_alchemy_conn_secret = sql_alchemy_conn
# You can also add a nested path
# example:
# sql_alchemy_conn_secret = core/sql_alchemy_conn
Copy to clipboard

This will retrieve config option from Secret Backends e.g Hashicorp Vault. See Secrets Backends for more details.

The following config options support this _cmd and _secret version:

  • sql_alchemy_conn in [core] section

  • fernet_key in [core] section

  • broker_url in [celery] section

  • flower_basic_auth in [celery] section

  • result_backend in [celery] section

  • password in [atlas] section

  • smtp_password in [smtp] section

  • bind_password in [ldap] section

  • git_password in [kubernetes] section

The _cmd config options can also be set using a corresponding environment variable the same way the usual config options can. For example:

export AIRFLOW__CORE__SQL_ALCHEMY_CONN_CMD=bash_command_to_run
Copy to clipboard

Similarly, _secret config options can also be set using a corresponding environment variable. For example:

export AIRFLOW__CORE__SQL_ALCHEMY_CONN_SECRET=sql_alchemy_conn
Copy to clipboard

The idea behind this is to not store passwords on boxes in plain text files.

The universal order of precedence for all configuration options is as follows:

  1. set as an environment variable (AIRFLOW__CORE__SQL_ALCHEMY_CONN)

  2. set as a command environment variable (AIRFLOW__CORE__SQL_ALCHEMY_CONN_CMD)

  3. set as a secret environment variable (AIRFLOW__CORE__SQL_ALCHEMY_CONN_SECRET)

  4. set in airflow.cfg

  5. command in airflow.cfg

  6. secret key in airflow.cfg

  7. Airflow’s built in defaults

Was this entry helpful?