This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch v2-11-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v2-11-test by this push:
new 9845555af4b Fix docs building after Google Provider link changed
9845555af4b is described below
commit 9845555af4b3c4d967ba3ba14ec10e0145ff1b50
Author: Jarek Potiuk <[email protected]>
AuthorDate: Tue Mar 31 10:31:32 2026 +0200
Fix docs building after Google Provider link changed
---
.../administration-and-deployment/production-deployment.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
a/docs/apache-airflow/administration-and-deployment/production-deployment.rst
b/docs/apache-airflow/administration-and-deployment/production-deployment.rst
index a341f7f1782..c740c60d841 100644
---
a/docs/apache-airflow/administration-and-deployment/production-deployment.rst
+++
b/docs/apache-airflow/administration-and-deployment/production-deployment.rst
@@ -249,14 +249,14 @@ If you are using Kubernetes Engine, you can use
`Workload Identity
<https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity>`__
to assign
an identity to individual pods.
-For more information about service accounts in the Airflow, see
:ref:`howto/connection:gcp`
+For more information about service accounts in the Airflow,
+see `GCP connection documentation
<https://airflow.apache.org/docs/apache-airflow-providers-google/stable/connections/gcp.html>`__.
Impersonate Service Accounts
----------------------------
-If you need access to other service accounts, you can
-:ref:`impersonate other service accounts <howto/connection:gcp:impersonation>`
to exchange the token with
-the default identity to another service account. Thus, the account keys are
still managed by Google
+If you need access to other service accounts, you can `impersonate other
service accounts
<https://airflow.apache.org/docs/apache-airflow-providers-google/stable/connections/gcp.html#direct-impersonation-of-a-service-account>`__.
+to exchange the token with the default identity to another service account.
Thus, the account keys are still managed by Google
and cannot be read by your workload.
It is not recommended to generate service account keys and store them in the
metadata database or the
