potiuk commented on issue #29918:
URL: https://github.com/apache/airflow/issues/29918#issuecomment-1459607775
We expose the information there also for connections and other things:
```
"connection-types": {
"type": "array",
"description": "Map of connection types mapped to hook class names.",
"items": {
"type": "object",
"properties": {
"connection-type": {
"description": "Type of connection defined by the provider",
"type": "string"
},
"hook-class-name": {
"description": "Hook class name that implements the connection
type",
"type": "string"
}
}
},
"required": ["connection-type", "hook-class-name"]
},
"extra-links": {
"type": "array",
"description": "Operator class names that provide extra link
functionality",
"items": {
"type": "string"
}
},
...
```
This is what I call "core extensions" - i.e. the ways how providers are
adding implementation of capabilities that Airflow exposes as public
interface. It is nicely summarized here (this page is automatically generated
based on the provider.yaml information, but also it is exposed for runtime
query via CLI (`airflow providers` subcommands such as `hooks`, `auth` etc.)
This information is automatically discovered via ProvidersManager based on
the information exposed via "get_provider_info" entrypoint (Providers Manager
automatically queries the installed providers to get that information and it
uses "provider_info.schema" to know how to query (simply get_provider_info
returns a dict that conforms to the schema which is selected subset of
information in provider.yaml.
https://airflow.apache.org/docs/apache-airflow-providers/core-extensions/index.html
This is in order to be able to actively "query" the providers and figure out
in automated way wha
--
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]
