You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Daniel Imberman (Jira)" <ji...@apache.org> on 2020/03/29 18:36:00 UTC

[jira] [Closed] (AIRFLOW-833) Sub-command to generate the default config

     [ https://issues.apache.org/jira/browse/AIRFLOW-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Imberman closed AIRFLOW-833.
-----------------------------------
    Resolution: Auto Closed

> Sub-command to generate the default config
> ------------------------------------------
>
>                 Key: AIRFLOW-833
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-833
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: cli
>            Reporter: George Sakkis
>            Assignee: George Sakkis
>            Priority: Major
>
> 1. Currently airflow autogenerates a default {{$AIRFLOW_HOME/airflow.cfg}} as soon as any command is issued or even when running {{import airflow}} from python, which IMO is rather intrusive (even more so when AIRFLOW_HOME defaults to the user's home directory).
> 2. Moreover, once the file is created it is not trivial to generate a default config again; one has to either move the existing one to another location or change (at least temporarily) AIRFLOW_HOME.
> Both issues can be addressed with the extension of the CLI with a subcommand to generate the default config explicitly at will instead of implicitly at import time.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)