airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Riccomini (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-16) Use GCP-specific fields in hook view
Date Fri, 29 Apr 2016 15:59:13 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264242#comment-15264242
] 

Chris Riccomini commented on AIRFLOW-16:
----------------------------------------

_Note: I am going to move the oauth2 upgrade to a separate JIRA, since it's a little decoupled
from this._

> Use GCP-specific fields in hook view
> ------------------------------------
>
>                 Key: AIRFLOW-16
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-16
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Chris Riccomini
>
> Once AIRFLOW-15 is done, we should update the Google cloud base hook to use fields for
project, service account, etc. We currently just use a JSON blob in the {{extras}} field.
We can steal this code from [this|https://github.com/airbnb/airflow/pull/1119/files] PR, where
{{extras\_\_google_cloud_platform_*}} is introduced in views.py.
> We should also look at creating just one hook of type google_cloud_platform, rather than
one hook per Google cloud service. Again, this is how the PR (above) works, and it's pretty
handy.



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

Mime
View raw message