Handle default values from Airflow 2 gracefully

[jedcunningham]

Apache Airflow version

main (development)

If "Other Airflow 2 version" selected, which one?

No response

What happened?

Some config options default values in Airflow 2 won't work well, possibly failing silently or not, in Airflow 3. An example is log_filename_template which silently breaks task logs in the new UI.

We should do a pass using all default config values from Airflow 2 and make sure, if they changed, that the old value folks may have in their existing config file may cause problems.

airflow config lint is likely a good place for handling this? Or depending on the situation, automatically upgrading the value and warning, like we've done in the past with log_filename_template in the past.

What you think should happen instead?

No response

How to reproduce

Create a airflow.cfg on Airflow 2, use it on Airflow 3.

Operating System

macos

Versions of Apache Airflow Providers

No response

Deployment

Virtualenv installation

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

[sunank200]

Draft PR: 47371

[sunank200]

I have made the changes. I will push the commit now after adding tests