airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-4971) Add Google Display & Video 360 integration
Date Mon, 23 Sep 2019 10:52:00 GMT

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

ASF GitHub Bot commented on AIRFLOW-4971:
-----------------------------------------

nuclearpinguin commented on pull request #6168: [AIRFLOW-4971] Add Google Display & Video
360 integration
URL: https://github.com/apache/airflow/pull/6168
 
 
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/)
issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-360
   
   ### Description
   
   - [ ] Here are some details about my PR, including screenshots of any UI changes:
   This PR adds operators for Google Display & Video 360 service.
   
   ### Tests
   
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely
good reason:
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines, and I have squashed
multiple commits if they address the same issue. In addition, my commits follow the guidelines
from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use
it.
     - All the public functions and the classes in the PR contain docstrings that explain
what it does
     - If you implement backwards incompatible changes, please leave a note in the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md)
so we can assign it to a appropriate release
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Add Google Display & Video 360 integration
> ------------------------------------------
>
>                 Key: AIRFLOW-4971
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4971
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: gcp
>    Affects Versions: 1.10.3
>            Reporter: Kamil Bregula
>            Priority: Major
>
> Hi
> This project lacks integration with the Google Display & Video 360 service. I would
be happy if Airflow had proper operators and hooks that integrate with this service.
> Product Documentation: https://developers.google.com/bid-manager/guides/getting-started-api
> API Documentation: https://developers.google.com/bid-manager/guides/getting-started-api
> Lots of love



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message