Airflow 2.3.0 does not keep promised backward compatibility regarding database configuration using _CMD Env

[c-thiel]

Apache Airflow version

2.3.0 (latest released)

What happened

We used to configure the Database using the AIRFLOW__CORE__SQL_ALCHEMY_CONN_CMD Environment variable.
Now the config option moved from CORE to DATABASE. However, we intended to keep backward compatibility as stated in the Release Notes.

Upon 2.3.0 update however, the _CMD suffixed variables are no longer recognized for database configuration in Core - I think due to a missing entry here:

airflow/airflow/configuration.py

Line 135 in 8622808

('database', 'sql_alchemy_conn'),

What you think should happen instead

We should only get a deprecation warning but the Database should be configured correctly.

How to reproduce

Configure Airflow using an external Database using the AIRFLOW__CORE__SQL_ALCHEMY_CONN_CMD environment variable. Notice that Airflow falls back to SQLight.

Operating System

kubernetes

Versions of Apache Airflow Providers

No response

Deployment

Other 3rd-party Helm chart

Deployment details

No response

Anything else

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[potiuk]

Indeed seems like a bug. Would you like to submit a PR fixing it @c-thiel ? Seems like an easy fix - and you could become one of the > 2000 contributors.