zachliu opened a new issue, #43794:
URL: https://github.com/apache/airflow/issues/43794

   ### Apache Airflow version
   
   2.10.3
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   In Airflow 2.10.3 `configuration.py` file, we have
   
   
https://github.com/apache/airflow/blob/c99887ec11ce3e1a43f2794fcf36d27555140f00/airflow/configuration.py#L857-L859
   
   The `self.sensitive_config_values` returns both `('database', 
'sql_alchemy_conn')` and `('core', 'sql_alchemy_conn')` because in 2.10.3 the 
[deprecated_options](https://github.com/apache/airflow/blob/c99887ec11ce3e1a43f2794fcf36d27555140f00/airflow/configuration.py#L328)
 variable is not empty. I think it's supposed to be removed. See 
https://github.com/apache/airflow/pull/42126.
   
   Hence the `self.get()` raises a warning:
   
   ```
   airflow/configuration.py:859 FutureWarning: section/key 
[core/sql_alchemy_conn] has been deprecated, you should 
use[database/sql_alchemy_conn] instead. Please update your `conf.get*` call to 
use the new name
   ```
   
   Which confuses our users.
   
   ### What you think should happen instead?
   
   The warning should be raised.
   
   ### How to reproduce
   
   1. `pip` Install Airflow 2.10.3
   2. Run cli `$ airflow version`
   
   ### Operating System
   
   Debian GNU/Linux 10 (buster)
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### 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
   
   - [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]

Reply via email to