Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D9BED200D1E for ; Wed, 4 Oct 2017 07:31:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D882B160BD5; Wed, 4 Oct 2017 05:31:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2A5C91609DE for ; Wed, 4 Oct 2017 07:31:04 +0200 (CEST) Received: (qmail 69727 invoked by uid 500); 4 Oct 2017 05:31:03 -0000 Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.incubator.apache.org Delivered-To: mailing list commits@airflow.incubator.apache.org Received: (qmail 69718 invoked by uid 99); 4 Oct 2017 05:31:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Oct 2017 05:31:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 6885E182E3C for ; Wed, 4 Oct 2017 05:31:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id MC8AXdo4WlrP for ; Wed, 4 Oct 2017 05:31:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4781C5F3FF for ; Wed, 4 Oct 2017 05:31:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 84442E0D34 for ; Wed, 4 Oct 2017 05:31:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1DAAD242DF for ; Wed, 4 Oct 2017 05:31:00 +0000 (UTC) Date: Wed, 4 Oct 2017 05:31:00 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AIRFLOW-1635) Allow creating Google Cloud Platform connection without requiring a JSON file MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 04 Oct 2017 05:31:05 -0000 [ https://issues.apache.org/jira/browse/AIRFLOW-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190834#comment-16190834 ] ASF subversion and git services commented on AIRFLOW-1635: ---------------------------------------------------------- Commit 6dec7acde3b599599cd83cfad3c84fc014b9931e in incubator-airflow's branch refs/heads/v1-9-test from [~barrywhart] [ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=6dec7ac ] [AIRFLOW-1635] Allow creating GCP connection without requiring a JSON file Closes #2640 from barrywhart/airflow-1635-gcp- json-data-master > Allow creating Google Cloud Platform connection without requiring a JSON file > ----------------------------------------------------------------------------- > > Key: AIRFLOW-1635 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1635 > 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 (v6.4.14#64029)