This is an automated email from the ASF dual-hosted git repository.

Miretpl 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 15e84188397 Document JSON connections in Azure Key Vault backend 
(#76650)
15e84188397 is described below

commit 15e84188397c711cf6eafd880b2763580d5f1fd0
Author: Thélio Matheus <[email protected]>
AuthorDate: Sun Nov 15 19:56:59 2026 -0300

    Document JSON connections in Azure Key Vault backend (#76650)
    
    The guide said a secret must hold a connection URI, even though the base
    secrets backend already parses JSON. JSON avoids URL-encoding by hand,
    which is error-prone for connections with several extras.
    
    Co-authored-by: Przemysław Mirowski 
<[email protected]>
---
 providers/microsoft/azure/docs/secrets-backends/azure-key-vault.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/providers/microsoft/azure/docs/secrets-backends/azure-key-vault.rst 
b/providers/microsoft/azure/docs/secrets-backends/azure-key-vault.rst
index 1925e2fa7d7..a4f4fbd7ac1 100644
--- a/providers/microsoft/azure/docs/secrets-backends/azure-key-vault.rst
+++ b/providers/microsoft/azure/docs/secrets-backends/azure-key-vault.rst
@@ -59,7 +59,7 @@ If you have set ``connections_prefix`` as 
``airflow-connections``, then for a co
 you would want to store your connection at 
``airflow-connections-smtp-default``.
 
 The value of the secret must be the :ref:`connection URI representation 
<generating_connection_uri>`
-of the connection object.
+or the :ref:`JSON representation <connection-serialization-json-example>` of 
the connection object.
 
 Storing and Retrieving Variables
 """"""""""""""""""""""""""""""""

Reply via email to