potiuk commented on issue #32048:
URL: https://github.com/apache/airflow/issues/32048#issuecomment-1663638068
I think it's quite easy - follow the way configs were moved to providers.
This is a very similar case.
1) add a "default_connections" config somewhere in provider.yaml (likely
"connection-types" should have an additional, optional fields
"default-connection" (should also be defined in provider_info.schema.json and
provider_yaml.schema.json) - expand ProivdersManager to also be aware of those
default connection (likely just changing schemas and .yaml files will be enough
becasue I think it uses dictionaries for "connection-types" - to be checked.
2) move the connections to all providers to be read from there.
3) add fall-back mechanism - move the list of "pre-2.8.0" (it will be
released in 2.8) default connections to an embedded declarative json/yaml file
to match providers with the connection that should be created if the provider
does not have the "default-connection" entries in their provider-info /
provider.yaml. This should cover the case where old providers are used with new
Airflow. This should also raise deprecation warning when accessed ("please
upgrade provider")
4) add all the extra stuff for discover: in CLI "airflow providers" and in
documentation - to have some information in our docs what are the default
connections contributed by each provider. This has the added benefit that it
will finally get documented - i.e from provider docs you will be able to see
what default connections are created.
--
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]
