This is an automated email from the ASF dual-hosted git repository. leahecole pushed a commit to branch fix-broken-link in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 9f1af6927a61c4c1cd5442d0234b047d9356217c Author: Leah E. Cole <[email protected]> AuthorDate: Fri Feb 18 16:22:25 2022 -0800 Update best-practices.rst I'm not sure how to view this in staging but I think I got the syntax right? I mimicked another one that referred to the top level code header. --- docs/apache-airflow/best-practices.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apache-airflow/best-practices.rst b/docs/apache-airflow/best-practices.rst index 3b01b3e..4dddaa53 100644 --- a/docs/apache-airflow/best-practices.rst +++ b/docs/apache-airflow/best-practices.rst @@ -199,7 +199,7 @@ If you want to use variables to configure your code, you should always use `environment variables <https://wiki.archlinux.org/title/environment_variables>`_ in your top-level code rather than :doc:`Airflow Variables </concepts/variables>`. Using Airflow Variables at top-level code creates a connection to metadata DB of Airflow to fetch the value, which can slow -down parsing and place extra load on the DB. See the `Airflow Variables <_best_practices/airflow_variables>`_ +down parsing and place extra load on the DB. See :ref:`best_practices/airflow_variables` on how to make best use of Airflow Variables in your DAGs using Jinja templates . For example you could set ``DEPLOYMENT`` variable differently for your production and development
