[
https://issues.apache.org/jira/browse/AIRFLOW-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800627#comment-16800627
]
ASF subversion and git services commented on AIRFLOW-3743:
----------------------------------------------------------
Commit a974c2dab9266392c8849e159d117eaf5d1a43cd in airflow's branch
refs/heads/v1-10-test from Ash Berlin-Taylor
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=a974c2d ]
fixup! [AIRFLOW-3743] Unify different methods of working out AIRFLOW_HOME
(#4705)
> 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
> Priority: Minor
> 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)
