You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/07/04 16:12:51 UTC

[GitHub] [airflow] dstandish commented on pull request #23560: Add advanced secrets backend configurations

dstandish commented on PR #23560:
URL: https://github.com/apache/airflow/pull/23560#issuecomment-1173975828

   yeah @potiuk I suggested that if we add this new way of configuring, we have to deprecate the old way.  @Taragolis has indicated that doing so is difficult / problematic / infeasible.  and there is the chicken egg problem.  and then there is the issue where if you're searching external backend for config values, well if you can support multiple multiple external backends that gets a bit messy.   all of which has brought be to the thinking that we ought to keep it simple and just make the search path orderable, more similar to the original PR.  really, the big win here will be being able to check env vars first.  _Indeed, maybe we should have done that from the beginning (env var -> external -> metastore)... but anyway..._  and if you really need multiple external backends you can wrap them in custom class.  that's my thinking anyway.


-- 
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