ssabdb commented on PR #43446: URL: https://github.com/apache/airflow/pull/43446#issuecomment-2456591689
For disclosure, I work with @claw89. Few more responses to question from @VladaZakharova. I should also add we are not Google, we're a small consulting company working with this product. > I think it should be a new, separate one. Ideally, providers should come with dashboards with system tests, similar to the ones we already have This is a [publicly documented](https://cloud.google.com/financial-services/anti-money-laundering/docs/concepts/overview) Google GA product, it's hard to see it fitting anywhere else in a different provider for in airflow-repository community supported providers. The procedure for adding a new provider involves a vote on the public list and I think it's unlikely we're going to get that passed (see [here](https://github.com/apache/airflow/blob/main/PROVIDERS.rst)), but I will concede a third party package is an option. > can you give us the reason why we want to add this new service to Google provider? Right now it looks like it has very narrow use case (it requires specific configuration to be able to run something using its API), so I would suggest not add it to Google provider without specific reason. We want to add it because there are several very large Google cloud customers (banks) who already use this API in production. They are either already using cloud composer and/or airflow to orchestrate related data workflows and this API is very data/data engineering workflow dependent. Bringing this in under the primary airflow repository would make it easier for them to adopt the AML AI product, since Airflow is often an approved product in these institutions or an obvious choice. Bringing in additional software often requires extra paperwork! We've observed more than one have resorted to building their own providers/hooks. I will concede that the usecase is narrow, but it's deep enough for Google to have released as a cloud product. We're also planning on adding addition operators. -- 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]
