[GitHub] [airflow] potiuk commented on issue #25555: Airflow doesn't re-use a secrets backend instance when loading configuration values

[GitBox <gi...@apache.org>]

potiuk commented on issue #25555:
URL: https://github.com/apache/airflow/issues/25555#issuecomment-1206628897

   This is not possible due to distributed nature of Airlfow. Secret client can be potentially use by scheduler and by multiuple workers - even if you just use a Local Executor you have potentially many independent processes and you cannot share client between the processes (even if they are forked, it is problematic, but when they are spawned it's impossible). 
   
   Solving the problem would require basically to implement some kind of agent that would shield connection from Airflow. Lucklily Vault has a ready-to use solution like that solves your problem - you just need to deploy it https://www.vaultproject.io/docs/agent/caching


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org