This is an automated email from the ASF dual-hosted git repository. joshfell 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 b33b11bf9f Update ref anchor for env var link in Connection how-to doc (#29816) b33b11bf9f is described below commit b33b11bf9fdbbedbd31699428853896f4db478cb Author: Josh Fell <48934154+josh-f...@users.noreply.github.com> AuthorDate: Thu Mar 2 13:05:18 2023 -0500 Update ref anchor for env var link in Connection how-to doc (#29816) In the "Managing Connections" how-to doc, the "environment variables" links in the doc point to the "Security of connections in the database" section rather than the "Storing connections in environment variables" section. --- docs/apache-airflow-providers-dbt-cloud/connections.rst | 2 +- docs/apache-airflow/cli-and-env-variables-ref.rst | 2 +- docs/apache-airflow/howto/connection.rst | 7 ++++--- 3 files changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/apache-airflow-providers-dbt-cloud/connections.rst b/docs/apache-airflow-providers-dbt-cloud/connections.rst index 2b0509dbab..1bd3945577 100644 --- a/docs/apache-airflow-providers-dbt-cloud/connections.rst +++ b/docs/apache-airflow-providers-dbt-cloud/connections.rst @@ -102,5 +102,5 @@ For example, to add a connection with the connection ID of "dbt_cloud_default": export AIRFLOW_CONN_DBT_CLOUD_DEFAULT='dbt-cloud://:api_to...@my-tenant.getdbt.com' You can refer to the documentation on -:ref:`creating connections via environment variables <environment_variables_secrets_backend>` for more +:ref:`creating connections via environment variables <environment_variables_connections>` for more information. diff --git a/docs/apache-airflow/cli-and-env-variables-ref.rst b/docs/apache-airflow/cli-and-env-variables-ref.rst index 7593233585..e2a929f1f4 100644 --- a/docs/apache-airflow/cli-and-env-variables-ref.rst +++ b/docs/apache-airflow/cli-and-env-variables-ref.rst @@ -90,7 +90,7 @@ Environment Variables For example, if you want to create a connection named ``PROXY_POSTGRES_TCP``, you can create a key ``AIRFLOW_CONN_PROXY_POSTGRES_TCP`` with the connection URI as the value. - For more information, see: :ref:`environment_variables_secrets_backend`. + For more information, see: :ref:`environment_variables_connections`. .. envvar:: AIRFLOW_HOME diff --git a/docs/apache-airflow/howto/connection.rst b/docs/apache-airflow/howto/connection.rst index 9b0e127f14..00b99de8ae 100644 --- a/docs/apache-airflow/howto/connection.rst +++ b/docs/apache-airflow/howto/connection.rst @@ -26,11 +26,13 @@ Airflow's :class:`~airflow.models.connection.Connection` object is used for stor Connections may be defined in the following ways: - - in :ref:`environment variables <environment_variables_secrets_backend>` + - in :ref:`environment variables <environment_variables_connections>` - in an external :doc:`/administration-and-deployment/security/secrets/secrets-backend/index` - in the :ref:`Airflow metadata database <connections-in-database>` (using the :ref:`CLI <connection/cli>` or :ref:`web UI <creating_connection_ui>`) +.. _environment_variables_connections: + Storing connections in environment variables -------------------------------------------- @@ -92,7 +94,7 @@ Storing connections in the database ----------------------------------- .. seealso:: - Connections can alternatively be stored in :ref:`environment variables <environment_variables_secrets_backend>` or an :doc:`external secrets backend </administration-and-deployment/security/secrets/secrets-backend/index>` such as HashiCorp Vault, AWS SSM Parameter Store, etc. + Connections can alternatively be stored in :ref:`environment variables <environment_variables_connections>` or an :doc:`external secrets backend </administration-and-deployment/security/secrets/secrets-backend/index>` such as HashiCorp Vault, AWS SSM Parameter Store, etc. When storing connections in the database, you may manage them using either the web UI or the Airflow CLI. @@ -179,7 +181,6 @@ Exporting connections to file You can export to file connections stored in the database (e.g. for migrating connections from one environment to another). See :ref:`Exporting Connections <cli-export-connections>` for usage. -.. _environment_variables_secrets_backend: Security of connections in the database ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^