Repository navigation
Fix deprecation warning on provider lookup in Amazon AWS hooks - #74480
Merged
vincbeck merged 1 commit intoOct 14, 2026
Merged
Conversation
Contributor
seanghaeli
approved these changes
Oct 9, 2026
seanghaeli
left a comment
Contributor
There was a problem hiding this comment.
Looks good, no risk of breaking anything
seanghaeli
approved these changes
Oct 9, 2026
Contributor
|
@ferruzzi could you merge this when you get a chance? |
|
Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix deprecated provider lookup in Amazon AWS hooks
AWS hooks emit a
DeprecatedImportWarningwhen adding the provider version to the boto3 user agent because they accessProvidersManager.hooks.Use
ProvidersManagerTaskRuntimewhen available, retaining the core manager as a fallback for older supported Airflow versions. Add a regression test that promotes the deprecated-hooks warning to an error and verifies the provider version is still returned.Was generative AI tooling used to co-author this PR?