potiuk commented on pull request #17625: URL: https://github.com/apache/airflow/pull/17625#issuecomment-899287726
This is not documentation change (yet). It's preparatory work and the main purpose is to prepare a common interface and communicatoin to both "community" providers developers as well as (and this is more important goal) to "custom providers writers" who get the tool to know about what and how they can customise in their own providers. Eventually "get_provider_info" provides summarized, queryeable, discoverable information about all things provider "provides" - not only those that require some "deep" integration, The main purpose is to get one place with information on capabilities of providers. This is purely informational one telling "this provider provides those features". It helps with discovery (again) if someone uses "providers" command (or in the future web ui). This is a good way to show what custom providers can deliver by exposing features of providers not only in the documentation, but also in the actual airlfow CLI, "customise providers" documentation, and webui. One of the best way to teach the users how they can add their own providers and expose such functionalities in similar way. Additional (more important) feature is that during our tests we are importing the classes exposed in `provider.yaml` and checking if they are properly configured (which also happens in runtime). This makes it easy to reason about any kind of typos you might have and you will see them early (as I did and fixed it while adding it). We are just about to add @taskgroups in the same way. This is about it. -- 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]
