Taishan314 opened a new issue, #39942:
URL: https://github.com/apache/airflow/issues/39942

   ### Description
   
   The current Search Ads 360 API is being deprecated and replaced with the 
Search Ads Reporting API, details of which are found 
[here](https://developers.google.com/search-ads/reporting/migrate/overview).
   
   I currently use the [GoogleSearchAds 
operators](https://github.com/apache/airflow/blob/main/airflow/providers/google/marketing_platform/operators/search_ads.py)
 which all call the GoogleSearchAdsHook, which in turn, establishes a 
connection to an api as seen 
[here](https://github.com/apache/airflow/blob/main/airflow/providers/google/marketing_platform/hooks/search_ads.py#L48).
   
   I believe this is calling the api soon to be deprecated. _**The deprecation 
date supplied by google is the 30th June 2024.**_
   
   ### Use case/motivation
   
   I'd like to see an update to this method to call the new api, perhaps make 
the old one optional for deprecation purposes.
   
   The old api service name is: _doubleclicksearch.googleapis.com_
   The new api service name is: _searchads360.googleapis.com_
   
   I believe the change should be adding the string "**_searchads360_**" to the 
build() method inside the get_conn() method call.
   
   Making that parameter configurable with the default as 
"**_doubleclicksearch_**" would be the ideal change for deprecation of the old 
api.
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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.

To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to