potiuk commented on PR #43446: URL: https://github.com/apache/airflow/pull/43446#issuecomment-2465896772
I am here with @michalmodras -> the example thing to separate from Google provider is `ads` - this had been a pain to keep in the same provider as other google properties and we want to split for quite some time. The problem with keeping "unrelated" APIs together is not only dependencies but also independent maintenance - upgrades when thing change. For example what happens if financial services API changes and drops support for older version, but other google APIs (say GKE) are fine running using older code? What happens if at the same time we have breaking changes in new providers for GKE - for example - and the users would not like to upgrade to new "google provider", but also they are using "google-finanacial" API and the old API in the "google provider" they want to keep, is not working any more? This is precisely what happened with ads provider. And If Google team wants to introduce and maintain the dashboard - that's ok. The condition for approving new provider is that there is **someone** who we can trust will keep an eye on it. It does not have to be original author - and here I see we have Google team confirming they will. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
