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/08/02 09:07:00 UTC

[jira] [Commented] (AIRFLOW-5095) airflow.cfg merger

    [ https://issues.apache.org/jira/browse/AIRFLOW-5095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16898716#comment-16898716 ] 

Ash Berlin-Taylor commented on AIRFLOW-5095:
--------------------------------------------

I don't quite understand what you mean here - with the config deprecation we already have in Airflow we sort of get this already.

I would rather we changed the way we generate airflow.cfg to _not_ include all the default values (as those are set already due to how we load config in Airflow)

> airflow.cfg merger
> ------------------
>
>                 Key: AIRFLOW-5095
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5095
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: cli
>    Affects Versions: 1.10.5
>            Reporter: Chao-Han Tsai
>            Assignee: Chao-Han Tsai
>            Priority: Major
>
> A CLI that can reads an old airflow.cfg and merge with the latest version of airflow.cfg



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)