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

   ### Apache Airflow version
   
   Other Airflow 2 version (please specify below)
   
   ### What happened
   
   I set a secrete as a variable and Airflow recognizes it as such and masks 
the value when trying to view the variables and when it is referenced in the 
logs. However, you can see the value when you click on “Task Instance Details” 
for a DAG that is using the variable. 
   MWAA 2.4.3
   
   
   ### What you think should happen instead
   
   The secret value should be masked.
   
   ### How to reproduce
   
   Add secret as a variable, name it password.
   Use the secret in a DAG, our example we were using it in the DAG overrides 
block. 
   Run an instance of the given DAG and navigate to the overrides section under 
'Task Instance Details"
   
   ### Operating System
   
   MWAA
   
   ### Versions of Apache Airflow Providers
   
   
   apache-airflow-providers-amazon | 6.0.0 | Amazon integration (including 
Amazon Web Services (AWS)).
   apache-airflow-providers-celery | 3.0.0 | Celery
   apache-airflow-providers-common-sql | 1.2.0 | Common SQL Provider
   apache-airflow-providers-ftp | 3.1.0 | File Transfer Protocol (FTP)
   apache-airflow-providers-http | 4.0.0 | Hypertext Transfer Protocol (HTTP)
   apache-airflow-providers-imap | 3.0.0 | Internet Message Access Protocol 
(IMAP)
   apache-airflow-providers-postgres | 5.2.2 | PostgreSQL
   apache-airflow-providers-sqlite | 3.2.1 | SQLite
   
   ### Deployment
   
   Amazon (AWS) MWAA
   
   ### Deployment details
   
   mwaa
   
   ### 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