[GitHub] [airflow] potiuk commented on issue #17604: Add an option to remove or mask environment variables in the KubernetesPodOperator task instance logs on failure or error events

potiuk commented on issue #17604: URL: https://github.com/apache/airflow/issues/17604#issuecomment-899099175 This is a different thing I believe. I think this is a coincidence and you habe "dbt_warehouse" (lowercase) set as an extra configuration in a connection. -- This is an automated

[GitHub] [airflow] potiuk commented on issue #17604: Add an option to remove or mask environment variables in the KubernetesPodOperator task instance logs on failure or error events

potiuk commented on issue #17604: URL: https://github.com/apache/airflow/issues/17604#issuecomment-898941231 WHOA! What a finding! Indeed - It looks like the secret_masker did not mask secret values in context exceptions. I just submitted PR #17618 fixing it - possibly just in

[GitHub] [airflow] potiuk commented on issue #17604: Add an option to remove or mask environment variables in the KubernetesPodOperator task instance logs on failure or error events

potiuk commented on issue #17604: URL: https://github.com/apache/airflow/issues/17604#issuecomment-898598673 OK. Thanks for the context. Really helpful. I think I know the problem, secret masker will not mask K8S env vars, it masks Airflow Variables. Maybe it is a good idea to add it then

[GitHub] [airflow] potiuk commented on issue #17604: Add an option to remove or mask environment variables in the KubernetesPodOperator task instance logs on failure or error events

potiuk commented on issue #17604: URL: https://github.com/apache/airflow/issues/17604#issuecomment-898467597 Which Airflow version are you running ? There is a "Secret Masker" feature in Airflow 2.1, and from what I understand it should also mask secret values