Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
Date: Tue, 3 May 2016 22:29:12 +0000 (UTC)
From: "Chris Riccomini (JIRA)" <jira@apache.org>
To: commits@airflow.incubator.apache.org
Message-ID: <JIRA.12964823.1462314507000.103194.1462314552821@Atlassian.JIRA>
In-Reply-To: <JIRA.12964823.1462314507000@Atlassian.JIRA>
References: <JIRA.12964823.1462314507000@Atlassian.JIRA> <JIRA.12964823.1462314507404@arcas>
Subject: [jira] [Created] (AIRFLOW-45) Support hidden Airflow variables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 03 May 2016 22:29:16 -0000

Chris Riccomini created AIRFLOW-45:
--------------------------------------

             Summary: Support hidden Airflow variables
                 Key: AIRFLOW-45
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-45
             Project: Apache Airflow
          Issue Type: Task
          Components: security
            Reporter: Chris Riccomini


We have a use case where someone wants to set a variable for their DAG, but they don't want it visible via the UI. I see that variables are encrypted in the DB (if the crypto package is installed), but the variables are still visible via the UI, which is a little annoying.

Obviously, this is not 100% secure, since you can still create a DAG to read the variable, but it will at least keep arbitrary users from logging in/loading the UI and seeing the variable.

I propose basically handling this the same way that DB hook passwords are handled. Don't show them in the UI when the edit button is clicked, but allow the variables to be editable.


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