You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2019/01/21 13:28:00 UTC

[jira] [Created] (AIRFLOW-3743) Unify multiple ways of specifying and accessing AIRFLOW_HOME

Ash Berlin-Taylor created AIRFLOW-3743:
------------------------------------------

             Summary: Unify multiple ways of specifying and accessing AIRFLOW_HOME
                 Key: AIRFLOW-3743
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3743
             Project: Apache Airflow
          Issue Type: Improvement
          Components: configuration
            Reporter: Ash Berlin-Taylor
            Assignee: Ash Berlin-Taylor
             Fix For: 1.10.3


We currently have two (or three, depending on how you look at it) ways of getting AIRFLOW_HOME

{{airflow.configuration.AIRFLOW_HOME}}
{{airflow.settings.AIRFLOW_HOME}}
{{airflow.configuration.get('core', 'airflow_home')}}

used throughout the codebase. This has led to a few odd bugs (https://github.com/puckel/docker-airflow/issues/225 for example) if the config file and environment are out-of-sync.

Since the default path of the config file is dependent on the AIRFLOW_HOME environment variable I propose we remove the airflow_home from the config file, and unify all access in the code base to go via {{settings.AIRFLOW_HOME}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)