ashb commented on pull request #19332: URL: https://github.com/apache/airflow/pull/19332#issuecomment-958930776
@potiuk That strikes me as a very-hard to reason about feature -- depending on _how_ the DAG accesses the variable means that you get different behaviour. If I do it one way the it will load the secret from the secrets store, but if I do it another way it will use the value in the env/DB. This makes the runtime behaviour hard to reason about and makes the system as a whole hard to reason about. This is a -1/veto from me, sorry. If you still want this sort of feature @raphaelauv then I would suggest you write a custom secrets backend (subclassing the existing GCS backend) and make a decision based on the name/prefix of the variable. That way the source of a variable doesn't depend on _how_ it is accessed in different DAGS. -- 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]
