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

   ### Apache Airflow version
   
   3.0.6
   
   ### If "Other Airflow 2 version" selected, which one?
   
   When running Airflow with [feature/component], sensitive values are not 
properly masked in [CLI / UI / logs / templates]. For example, the rendered 
template shows the actual value instead of the masked
   
   ### What happened?
   
   When running Airflow with [feature/component], sensitive values are not 
properly masked in [CLI / UI / logs / templates]. For example, the rendered 
template shows the actual value instead of the masked ***.
   
   ### What you think should happen instead?
   
   Airflow should consistently apply secret masking across all outputs, 
including [CLI logs, rendered templates, UI, etc.]. Any sensitive values should 
be replaced with
   
   ### How to reproduce
   
   Start Airflow with [describe environment: local docker-compose, Helm, etc.]
   
   Configure a connection/secret containing sensitive values (e.g., API key, 
password).
   
   Trigger a DAG that renders or logs the connection string.
   
   Observe that the actual value appears unmasked in [CLI/UI/logs].
   
   ### Operating System
   
   Ubuntu 22.04 LTS, macOS 13, etc. – output from cat /etc/os-release
   
   ### Versions of Apache Airflow Providers
   
   pip freeze | grep apache-airflow-providers
   
   ### Deployment
   
   Amazon (AWS) MWAA
   
   ### 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