Validate TriggerDagRunOperator logical_date after template rendering - #70490
Conversation
logical_date is a template field, but its type validation ran in __init__, before Jinja rendering. Validate in execute() instead so the rendered value is what gets checked.
boring-cyborg
Bot
added
area:dev-tools
area:providers
backport-to-v3-3-test
|
re-run the CI test |
|
Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions. |
Backport failed to create: v3-3-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 6bef2b4 v3-3-testThis should apply the commit to the v3-3-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
3 participants
logical_dateis a template field ofTriggerDagRunOperator, but its str/datetime/None type validation ran in__init__, before Jinja rendering. The check now runs at the top ofexecute()on the rendered value (run_afterkeeps its constructor validation — it is not a template field). Removes the class from the exemption list.related: #70296
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Fable 5) following the guidelines