This is an automated email from the ASF dual-hosted git repository.
taragolis pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new b9c38c6b18 DOC multiple vault mount points (#36313)
b9c38c6b18 is described below
commit b9c38c6b18412179afca11aea5d68f416e7bcafd
Author: Noël Bardelot <[email protected]>
AuthorDate: Wed Dec 20 12:18:51 2023 +0100
DOC multiple vault mount points (#36313)
* DOC multiple vault mount points
* Update
docs/apache-airflow-providers-hashicorp/secrets-backends/hashicorp-vault.rst
Co-authored-by: Andrey Anshin <[email protected]>
* Update
docs/apache-airflow-providers-hashicorp/secrets-backends/hashicorp-vault.rst
Co-authored-by: Andrey Anshin <[email protected]>
---------
Co-authored-by: Noël Bardelot <[email protected]>
Co-authored-by: Andrey Anshin <[email protected]>
---
.../secrets-backends/hashicorp-vault.rst | 31 +++++++++++++++++++++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git
a/docs/apache-airflow-providers-hashicorp/secrets-backends/hashicorp-vault.rst
b/docs/apache-airflow-providers-hashicorp/secrets-backends/hashicorp-vault.rst
index f94ae7edcb..6816258e0d 100644
---
a/docs/apache-airflow-providers-hashicorp/secrets-backends/hashicorp-vault.rst
+++
b/docs/apache-airflow-providers-hashicorp/secrets-backends/hashicorp-vault.rst
@@ -169,7 +169,7 @@ Note that the secret ``Key`` is ``value``, and secret
``Value`` is ``world`` and
``mount_point`` is ``airflow``.
Storing and Retrieving Config
-""""""""""""""""""""""""""""""""
+"""""""""""""""""""""""""""""
If you have set ``config_path`` as ``config`` and ``mount_point`` as
``airflow``, then for config ``sql_alchemy_conn_secret`` with
``sql_alchemy_conn_value`` as value, you would want to store your secret as:
@@ -214,3 +214,32 @@ Add "verify": "absolute path to ca-certificate file"
[secrets]
backend = airflow.providers.hashicorp.secrets.vault.VaultBackend
backend_kwargs = {"connections_path": "airflow-connections",
"variables_path": null, "mount_point": "airflow", "url":
"http://127.0.0.1:8200";, "verify": "/etc/ssl/certs/ca-certificates"}
+
+Using multiple mount points
+"""""""""""""""""""""""""""
+
+You can use multiple mount points to store your secrets. For example, you
might want to store the Airflow instance configurations
+in one Vault KV engine only accessible by your Airflow deployment tools, while
storing the variables and connections in another KV engine
+available to your DAGs, in order to grant them more specific Vault ACLs.
+
+In order to do this, you will need to setup you configuration this way:
+
+* leave ``mount_point`` as JSON ``null``
+* if you use ``variables_path`` and/or ``connections_path``, set them as
``"mount_point/path/to/the/secrets"``
+ (the string will be split using the separator ``/``, the first element will
be the mount point, the remaining
+ elements will be the path to the secrets)
+* leave ``config_path`` as the empty string ``""``
+* if you use ``config_path``, each configuration item will need to be prefixed
with the ``mount_point`` used for configs,
+ as ``"mount_point/path/to/the/config"`` (here again, the string will be
split using the separator ``/``,
+ the first element will be the mount point, the remaining elements will be
the path to the configuration parameter)
+
+For example:
+
+.. code-block:: ini
+
+ [core]
+ sql_alchemy_conn_secret:
"deployment_mount_point/airflow/configs/sql_alchemy_conn_value"
+
+ [secrets]
+ backend = airflow.providers.hashicorp.secrets.vault.VaultBackend
+ backend_kwargs = {"connections_path":
"dags_mount_point/airflow/connections", "variables_path":
"dags_mount_point/airflow/variables", "config_path": "", mount_point": null,
"url": "http://127.0.0.1:8200";, "verify": "/etc/ssl/certs/ca-certificates"}
