This is an automated email from the ASF dual-hosted git repository.
jedcunningham pushed a commit to branch v2-2-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
commit c03b086e488229857d6ca49a715f3120112ed3c8
Author: Madison Swain-Bowden <bowd...@spu.edu>
AuthorDate: Tue Feb 15 13:56:00 2022 -0800
Add note about Variable precedence with env vars (#21568)
This PR updates some documentation regarding setting Airflow Variables
using environment variables. Environment variables take precedence over
variables defined in the UI/metastore based on this default search path list:
https://github.dev/apache/airflow/blob/7864693e43c40fd8f0914c05f7e196a007d16d50/airflow/secrets/__init__.py#L29-L30
(cherry picked from commit 7a268cb3c9fc6bc03f2400c6632ff8dccf4e451e)
---
docs/apache-airflow/howto/variable.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/docs/apache-airflow/howto/variable.rst
b/docs/apache-airflow/howto/variable.rst
index 7cb9377..401dcb1 100644
--- a/docs/apache-airflow/howto/variable.rst
+++ b/docs/apache-airflow/howto/variable.rst
@@ -62,7 +62,8 @@ You can use them in your DAGs as:
Single underscores surround ``VAR``. This is in contrast with the way
``airflow.cfg``
parameters are stored, where double underscores surround the config
section name.
Variables set using Environment Variables would not appear in the Airflow
UI but you will
- be able to use them in your DAG file.
+ be able to use them in your DAG file. Variables set using Environment
Variables will also
+ take precedence over variables defined in the Airflow UI.
Securing Variables
------------------
