potiuk commented on PR #36492: URL: https://github.com/apache/airflow/pull/36492#issuecomment-1872474138
> We usually access secrets from either disk or connections or encrypted variables in airflow Correct. This is possible, no doubt about it. But it might quite a bit complex for a number of Triggers. I am not sure how the `async_hook` works. But if you would like to use Airflow's Connection (either from the DB or from Secrets) I think it would not work (It would need async-aware access to the DB or Secrets). I would love to see how it can work in this case ? Could you please explain it - maybe I am missing something? I believe it uses the built-in async credental/session retrieval but that would not use Airfow's Connections/Secrets? Or am I wrong ? Also in some cases (like for example when authentication information is coming from externally mounted volumes) is simply not available. Good exmple is when you have a managed service where the authentication information is available on a mounted volume, but the volume is not mounted in Triggerer. . Yes. This is a limitation of this particular service, but it also shows a more general problem where Triggerer would need generally the same auth environment that worker (which might not be desired or possible). -- 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-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
