[
https://issues.apache.org/jira/browse/AIRFLOW-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16805458#comment-16805458
]
ASF subversion and git services commented on AIRFLOW-3540:
----------------------------------------------------------
Commit 540612253d2f743ebc1def91fda8c9b3e36ff8bd in airflow's branch
refs/heads/v1-10-stable from Ash Berlin-Taylor
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=5406122 ]
[AIRFLOW-3540] Warn if old airflow.cfg file is found (#5006)
We used to read this config file, but we now don't. To make it easier on
users (particularly of puckel's docker container) lets at least issue a
warning
> Presence of ~/airflow/airflow.cfg shouldn't override config file settings
> -------------------------------------------------------------------------
>
> Key: AIRFLOW-3540
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3540
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Josh Carp
> Assignee: Josh Carp
> Priority: Trivial
> Fix For: 1.10.3
>
>
> If `~/airflow/airflow.cfg` exists, airflow uses that file instead of
> `$AIRFLOW_HOME/airflow.cfg`. This behavior is confusing. If `$AIRFLOW_HOME`
> is set and `$AIRFLOW_CONFIG` is not, we should only check
> `$AIRFLOW_HOME/airflow.cfg`.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
