Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
Date: Sat, 11 Jun 2016 19:26:20 +0000 (UTC)
From: "Jakob Homan (JIRA)" <jira@apache.org>
To: commits@airflow.incubator.apache.org
Message-ID: <JIRA.12977887.1465673152000.62538.1465673180928@Atlassian.JIRA>
In-Reply-To: <JIRA.12977887.1465673152000@Atlassian.JIRA>
References: <JIRA.12977887.1465673152000@Atlassian.JIRA> <JIRA.12977887.1465673152562@arcas>
Subject: [jira] [Created] (AIRFLOW-236) Support passing S3 credentials
 through environmental variables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 11 Jun 2016 19:26:26 -0000

Jakob Homan created AIRFLOW-236:
-----------------------------------

             Summary: Support passing S3 credentials through environmental variables
                 Key: AIRFLOW-236
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-236
             Project: Apache Airflow
          Issue Type: Improvement
          Components: core
            Reporter: Jakob Homan


Right now we expect S3 configs to be passed through one of a variety of config files, or through extra parameters in the connection screen.  It'd be nice to be able to pass these through env variables and note as such through the extra parameters.  This would lessen the need to include credentials in the webapp itself.

Alternatively, for logging (rather than as a connector), it might just be better for Airflow to use the profie defined as AWS_DEFAULT and avoid needed an explicit configuration at all.


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