You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2016/04/28 18:31:12 UTC
[jira] [Updated] (AIRFLOW-16) Use GCP-specific fields in hook view
[ https://issues.apache.org/jira/browse/AIRFLOW-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Riccomini updated AIRFLOW-16:
-----------------------------------
Description:
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.
was:
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.
> 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)