rawwar commented on issue #39378: URL: https://github.com/apache/airflow/issues/39378#issuecomment-2094757521
> In this case it is required not only change implementation in hoop but also change in operators, sensors, triggers. For each cloud provider with own auth methods 🙄 Would it be a good idea to implement a dialect like `sqlalchemy` does? This would allow the user to provide the necessary details and the dialect, and internally, we would choose the appropriate hook. This approach would make it easier to maintain or extend the system, especially when multiple hooks cater to different types of backend systems while the user will always use a single operator class with varying arguments -- 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]
