potiuk commented on PR #39243: URL: https://github.com/apache/airflow/pull/39243#issuecomment-2119291434
Why not just adding it to `microsoft.azure` then? Adding new provider to manage, is quite an overhead (and to remind again - it would require devlist discussion). Adding just an operator to microsoft.azure seems to be preferred. Unless you think of course Fabric provider deserves to be separated for some reason. Also I think starting devlist discussion is a good start to see how Microsoft is going to possibly support their providers via system tests similarly to Amazon and (soon) Google. Both Amazon and Google team developed and maintain and (Google soon) publish dashboards with system tests / example dags run in their systems that give the community (and AWS/Google teams) opportunity to see and fix any problems resulting with real services. That might be great opportunity for Microsoft to become more visible as stakeholder and follow the good practices of others. -- 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]
