Taragolis commented on code in PR #23560:
URL: https://github.com/apache/airflow/pull/23560#discussion_r913123196
##########
airflow/config_templates/default_airflow.cfg:
##########
@@ -422,6 +422,13 @@ backend =
# ``{{"connections_prefix": "/airflow/connections", "profile_name":
"default"}}``
backend_kwargs =
+# Advanced secrets backend configuration, allow to user configure more than
one secret backend,
+# order of secrets backend and turn off built-in backends.
+# Expected JSON list of objects. See
+#
https://airflow.apache.org/docs/apache-airflow/stable/security/secrets/secrets-backend/index.html#advanced-configuration
+# for more details.
+backends_config =
Review Comment:
> This might happen that someone will set the three of them, and
backends_config should get precedence
I can't find the good way how to do it right now with
`AirflowConfigParser.deprecated_options`, because if we put this configs as
deprecated and try to check is user actually put something in this config the
result will - deprecation warning every time even if user do not use that.
I think I do not try only one option - get this configs without fallback, in
this case probably we only have to catch exception and no deprecation warnings
raised in case if user do not set anything. It just my assuming.
Another interesting moment it would a first time when one config option
replace two options but right now all deprecation expected one-to-one
--
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]
