[ 
https://issues.apache.org/jira/browse/AIRFLOW-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jarek Potiuk updated AIRFLOW-3524:
----------------------------------
    Description: 
In order to enable automated execution of integration tests for GCP operators 
we need to synchronise naming of the variables and add some setup/teardown 
codes for some of the operators so that the tests can be run in an automated 
way.

This will be quite a refactor across GCP compute, compute_igm, gcf, cloudsql 
and a little in dataproc, container, s3to gcf. It will be followed by another 
change that will allow to run it all via Google Cloud Build on a Google 
infrastructure.

It's a proof of concept for GCP-enabled implementation of 
[https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-4+Support+for+Integration+Tests]
 (which will be changed accordingly to make it GCP-ony support). Google Cloud 
Build allows for super-easy automation of those tests.

  was:
In order to enable automated execution of integration tests for GCP operators 
we need to synchronise naming of the variables and add some setup/teardown 
codes for some of the operators so that the tests can be run in an automated 
way.

This will be quite a refactor across GCP compute, compute_igm, gcf, cloudsql 
and a little in dataproc, container, s3to gcf. It will be followed by another 
change that will allow to run it all via Google Cloud Build on a Google 
infrastructure.

It's a proof of concept for GCP-enabled implementation of 
[https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-4+Support+for+Integration+Tests]
 (which will be changed accordingly to make it GCP-ony support). Google Cloud 
Build is very well integrated into GCP operations.

 


> Enable automated execution of integration tests for GCP operators
> -----------------------------------------------------------------
>
>                 Key: AIRFLOW-3524
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3524
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Jarek Potiuk
>            Priority: Major
>
> In order to enable automated execution of integration tests for GCP operators 
> we need to synchronise naming of the variables and add some setup/teardown 
> codes for some of the operators so that the tests can be run in an automated 
> way.
> This will be quite a refactor across GCP compute, compute_igm, gcf, cloudsql 
> and a little in dataproc, container, s3to gcf. It will be followed by another 
> change that will allow to run it all via Google Cloud Build on a Google 
> infrastructure.
> It's a proof of concept for GCP-enabled implementation of 
> [https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-4+Support+for+Integration+Tests]
>  (which will be changed accordingly to make it GCP-ony support). Google Cloud 
> Build allows for super-easy automation of those tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to