airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AIRFLOW-1635) Allow creating Google Cloud Platform connection without requiring a JSON file
Date Wed, 04 Oct 2017 05:31:00 GMT


ASF subversion and git services commented on AIRFLOW-1635:

Commit 6dec7acde3b599599cd83cfad3c84fc014b9931e in incubator-airflow's branch refs/heads/v1-9-test
from [~barrywhart]
[;h=6dec7ac ]

[AIRFLOW-1635] Allow creating GCP connection without requiring a JSON file

Closes #2640 from barrywhart/airflow-1635-gcp-

> Allow creating Google Cloud Platform connection without requiring a JSON file
> -----------------------------------------------------------------------------
>                 Key: AIRFLOW-1635
>                 URL:
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: gcp
>    Affects Versions: 1.8.2
>            Reporter: Barry Hart
>            Assignee: Barry Hart
>             Fix For: 1.10.0
>         Attachments: AIRFLOW-1635.png
> Most connection types can be created purely from the Airflow UI. Google Cloud Platform
connections do not support this, because they require a JSON file to be present on disk. This
is awkward for users who only have UI access (i.e. no direct access to the server's file system)
because it requires coordination with a system administrator to add or update a connection.
> I propose that Airflow offer two ways to set up a Google cloud connection:
> * The current method of placing a file on disk and entering its path.
> * New method where the Airflow user/administrator pastes the JSON *contents* into the
Airflow UI. This will be a new field in the UI.
> If both a path and JSON data are provided, the path will take precedence. This is somewhat
arbitrary; typically only one field would contain a value.

This message was sent by Atlassian JIRA

View raw message