Validate AppflowBaseOperator source after template rendering - #70482
Validate AppflowBaseOperator source after template rendering#70482mitre88 wants to merge 2 commits into
Conversation
source is a template field, but it was validated in __init__, which runs before Jinja rendering — so any templated value was rejected at Dag parse time. Validate in execute() instead, where the rendered value is available.
|
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
|
|
The test should also validate a templated value actually passes the test. The current test also passed without the change to implementation. |
|
Thanks for the review! Added One note on scope: the Drafted-by: Claude Code (Fable 5) (no human review before posting) |
|
Closing — #70440 merged a more complete version of this: it moves the base-class check to execute time and also converts the Drafted-by: Claude Code (Fable 5) (no human review before posting) |
sourceis one ofAppflowBaseOperator's template fields, but it was validated againstSUPPORTED_SOURCESinside__init__, which runs before Jinja rendering — so a templatedsourcewas rejected at Dag parse time with the raw expression in the error message. This moves the check to the top ofexecute(), where the rendered value is available, and 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