Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
Date: Wed, 15 Jun 2016 19:22:09 +0000 (UTC)
From: "Kengo Seki (JIRA)" <jira@apache.org>
To: commits@airflow.incubator.apache.org
Message-ID: <JIRA.12977361.1465501844000.9582.1466018529594@Atlassian.JIRA>
In-Reply-To: <JIRA.12977361.1465501844000@Atlassian.JIRA>
References: <JIRA.12977361.1465501844000@Atlassian.JIRA> <JIRA.12977361.1465501844391@arcas>
Subject: [jira] [Updated] (AIRFLOW-227) Show environmentally defined configs
 in the config view
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 15 Jun 2016 19:22:14 -0000


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

Kengo Seki updated AIRFLOW-227:
-------------------------------
    External issue URL: https://github.com/apache/incubator-airflow/pull/1597

> Show environmentally defined configs in the config view
> -------------------------------------------------------
>
>                 Key: AIRFLOW-227
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-227
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: webserver
>            Reporter: Jakob Homan
>            Assignee: Kengo Seki
>
> Right now the config page (when set to display) just loads the airflow.cfg and lists that.   This means that any configuration values that are set via an environment variable are not shown.
> On the one hand, this is nice for secure values (ie, db connect string), but becomes a pain if large amounts of configuration are done throgh env vars.  This situation can occur when deploying airflow in production versus staging versus dev environments.  We currently load lots of values through env vars (passed into the Docker containers).  These values don't show up in the config screen.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)