kaxil commented on issue #19251:
URL: https://github.com/apache/airflow/issues/19251#issuecomment-958981398
Another possible solution I can think of is to build another Secret Backend
that actually allows "skipping" touching the "external" secret backend entirely
for some conditions ("prefix", "patterns"). So users don't need to update all
their DAGs when they need to change something and will be a single source of
truth of where the values for this variable/connection comes from.
For observability, we can probably create a page under "Admin" of where this
secret comes from (similar to our airflow configuration page that has **Running
Configurations**).
--
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]
