This is an automated email from the ASF dual-hosted git repository. ephraimanierobi pushed a commit to branch v2-5-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 1ed564fbee9a11a56b007151c8ad09a0d12c0932 Author: Mayeul Kauffmann <[email protected]> AuthorDate: Thu Mar 2 18:37:13 2023 +0100 Correct link to best_practice(s) section (#29876) Logical link <best_practices/airflow_variables> fails. In similar file faq.rst, logical link `DAG writing best practices<best_practice:writing_a_dag>` (without "s" at practice) works. (cherry picked from commit 43d48e17dc18d81d620c9e90758078f152762d74) --- docs/apache-airflow/howto/dynamic-dag-generation.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apache-airflow/howto/dynamic-dag-generation.rst b/docs/apache-airflow/howto/dynamic-dag-generation.rst index f180183631..5d542a2932 100644 --- a/docs/apache-airflow/howto/dynamic-dag-generation.rst +++ b/docs/apache-airflow/howto/dynamic-dag-generation.rst @@ -40,7 +40,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 </core-concepts/variables>`. Using Airflow Variables in top-level code creates a connection to the metadata DB of Airflow to fetch the value, which can slow -down parsing and place extra load on the DB. See the `best practices on Airflow Variables <best_practices/airflow_variables>`_ +down parsing and place extra load on the DB. See the `best practices on Airflow Variables <best_practice:airflow_variables>`_ to make the best use of Airflow Variables in your DAGs using Jinja templates. For example you could set ``DEPLOYMENT`` variable differently for your production and development
