Remove duplicated connection-type within the provider #26628
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove duplicated connection type for amazon and databricks providers.
aws
provided byairflow.providers.amazon.aws.hooks.base_aws.AwsGenericHook
databricks
provided byairflow.providers.databricks.hooks.databricks.DatabricksHook
Seem like the actual order in connection-types in
provider.yaml
the only thing that really matter, if provider contains multiple differenthook-class-name
with the sameconnection-type
:hook-class-name
with listed would use in the UI/API/CLI for fields names and testing connectionconnection-type
exists in the different providersairflow/airflow/providers_manager.py
Lines 529 to 539 in 55d1146
Might be also good idea to warn users if already_registered
connection-type
exists in the same provider.