sswander opened a new issue, #33946: URL: https://github.com/apache/airflow/issues/33946
### Apache Airflow version 2.7.0 ### What happened Using Airflow 2.7.0, running the following command does not result in airflow.cfg being created ```sh $ AIRFLOW_HOME=~/airflow_test airflow --help $ ls ~/airflow_test logs # <-- should include airflow.cfg too ``` **Further background info** Our 3rd party tool invokes `airflow --help` to create a airflow.cfg file into a custom AIRFLOW_HOME env. ### What you think should happen instead The 2.7.0 docs mentioned that it will create airflow.cfg in custom AIRFLOW_HOME https://airflow.apache.org/docs/apache-airflow/2.7.0/howto/set-config.html Therefore, ### How to reproduce Using virtualenv to conveniently reproduce: ```sh virtualenv test_airflow_270 . test_airflow_270/bin/activate (test_airflow_270) -> ~ pip install apache-airflow=2.7.0 (test_airflow_270) -> ~ AIRFLOW_HOME=~/airflow270_test_home airflow --help (test_airflow_270) -> ~ ls ~/airflow270_test_home # -> does not contain airflow.cfg ``` ### Operating System macOS Ventura `13.5.1 (22G90)` ### Versions of Apache Airflow Providers _No response_ ### Deployment Virtualenv installation ### Deployment details _No response_ ### Anything else This behaved according to the docs in Airflow 2.6.3, but in Airflow 2.7.0 it stopped working ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
