Taragolis commented on code in PR #23560:
URL: https://github.com/apache/airflow/pull/23560#discussion_r914257501


##########
docs/apache-airflow/security/secrets/secrets-backend/index.rst:
##########
@@ -73,6 +74,47 @@ the example below.
     $ airflow config get-value secrets backend
     
airflow.providers.google.cloud.secrets.secret_manager.CloudSecretManagerBackend
 
+Advanced Configuration
+""""""""""""""""""""""
+
+.. versionadded:: 2.4.0
+
+You can provide ``backends_config`` with json-list which contains json-objects 
of required backends for:
+
+* Configure more than one alternative secrets backend.
+* Change search ordering of secrets backends.
+* Turn off built-in backends (environment variables or the metastore database).
+
+Object should contains mandatory **backend** attribute with fully qualified 
class name of the backend you want to enable
+and optionally contains **backend_kwargs** with json-object which will be 
passed as kwargs to the ``__init__``
+method of your secrets backend.
+
+Here's a basic example of how to configure to use Environment Variables first,
+next :ref:`SSM Parameter Store <ssm_parameter_store_secrets>`, and then 
metastore.:
+
+.. code-block:: json
+
+    [
+      {
+        "backend": 
"airflow.secrets.environment_variables.EnvironmentVariablesBackend"
+      },
+      {
+        "backend": 
"airflow.providers.amazon.aws.secrets.systems_manager.SystemsManagerParameterStoreBackend",
+        "backend_kwargs": {
+          "connections_prefix": "/airflow/connections",
+          "profile_name": "default"
+        }
+      },
+      {
+        "backend": "airflow.secrets.metastore.MetastoreBackend"
+      }
+    ]
+
+.. warning::
+
+    If you specify ``backends_config`` options than Airflow will ignore values
+    in ``backend`` and ``backend_kwargs`` options.

Review Comment:
   If I configure `AIRFLOW__CORE__SQL_ALCHEMY_CONN` and 
`AIRFLOW__DATABASE__SQL_ALCHEMY_CONN` in airflow 2.3.x then 
`AIRFLOW__CORE__SQL_ALCHEMY_CONN` would ignored, am I right?
   
   Anyway if we decide deprecate old values in some new version then better 
remove information about old configuration with warning if user use old 
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]

Reply via email to