Fix reversed credential precedence in Bedrock hook docstring - #71826
Open
Lee-W wants to merge 1 commit into
Open
Fix reversed credential precedence in Bedrock hook docstring#71826Lee-W wants to merge 1 commit into
Lee-W wants to merge 1 commit into
Conversation
The PydanticAIBedrockHook docstring listed IAM keys before the bearer token, but BedrockProvider.__init__ in pydantic-ai checks api_key / AWS_BEARER_TOKEN_BEDROCK first and never passes the IAM key args to boto3 when it is set, so the bearer token actually wins when both are configured. Caught during review of apache#71774, which already documents the correct precedence on the connection docs page.
SameerMesiah97
approved these changes
Aug 19, 2026
amoghrajesh
approved these changes
Aug 20, 2026
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
3 participants
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.
The PydanticAIBedrockHook docstring listed IAM keys before the bearer token, but
BedrockProvider.__init__in pydantic-ai checks api_key / AWS_BEARER_TOKEN_BEDROCK first and never passes the IAM key args to boto3 when it is set, so the bearer token actually wins when both are configured.Was generative AI tooling used to co-author this PR?
Generated-by: [Claude] following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.