ssabdb commented on PR #43446: URL: https://github.com/apache/airflow/pull/43446#issuecomment-2457628461
I think the issues are: 1) Creating a new, google provider will need some considerable design work - which providers should we split out? How? We can start with a cloudai provider, but I don't know enough about the best way to split this out. 2) This PR does not introduce any additional dependencies, which seems to be the motivation behind the Google provider in https://github.com/apache/airflow/issues/15933 3) Creating a new environment will also involve setting up and appropriately resourcing the build test dashboard. As a small organization, we're not in a position to be running and owning the CI and resultant dashboard for dozens of Google services. 4) As @potiuk has pointed out on that thread, a full blocking process > It will not be "split and done". My point here is that this is a long-haul and requires to work out the process of maintenance, managing to respond to user's questions, document it properly, make frequent decisions on whether to accept and release changes that are "possibly" incompatible and how to version those separate providers and core. If the intention/new policy is that any additional services added to the google provider should be channelled down as an incremental process as a path to close https://github.com/apache/airflow/issues/15933, fine - but it's going to be quite confusing to users in the meantime and requires a proper roadmap rather than a piecemeal approach. Otherwise, I'm concerned that https://github.com/apache/airflow/issues/15933 has been open for 3 years now and blocking incremental additions behind what is outwardly a considerable change doesn't seem to have happened elsewhere - unless work is already underway? -- 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]
