A good way to go about it would be to leverage an environment variable AIRFLOW__CORE__SENSITIVE_VAR_CONN_NAMES where you can pass a comma-separated list of extra sensitive keywords to look for in variables names or connection’s extra JSON.
This way you will see *** both in the Rendered Template and Task Instance Details.
HI @magdagultekin, I am also facing a similar kind of issue.
I set the following astro env variables with the given values
But still the airflow connections extra json’s private key remains a visible text