Move template-field validation/transformation out of init for Amazon Bedrock operators - #70306
Merged
Conversation
Avcu
force-pushed
the
init_refactor
branch
2 times, most recently
from
July 23, 2026 17:58
260c24c to
b3cea95
Compare
78 tasks
Avcu
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
potiuk
as code owners
July 23, 2026 22:54
shahar1
approved these changes
Jul 24, 2026
Keeping resolved operators in the exemption list hides regressions and causes the burn-down tracker to drift from actual code state. This keeps the pre-commit guard aligned with what still needs migration.
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.
Template fields are rendered only after operators' constructor runs. Therefore, I moved the field transformation logic out of
__init__for Amazon Bedrock operators. I added specific unit tests to verify the updated logic.Was generative AI tooling used to co-author this PR?
{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.