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, 27 Sep 2017 17:29:02 GMT


ASF subversion and git services commented on AIRFLOW-1635:

Commit e2ee8f53fb4747a3e7fac22b987dd74386d61765 in incubator-airflow's branch refs/heads/v1-8-test
from [~criccomini]
[;h=e2ee8f5 ]

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

This reverts commit 50d0d5b0bcbbd18d2c76d788e22bfdcc2c0d6f71.

> 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