Skip to content

Allow templated fields in AppFlow operators#70440

Open
fat-catTW wants to merge 1 commit into
apache:mainfrom
fat-catTW:fix-appflow-template-field-validation
Open

Allow templated fields in AppFlow operators#70440
fat-catTW wants to merge 1 commit into
apache:mainfrom
fat-catTW:fix-appflow-template-field-validation

Conversation

@fat-catTW

Copy link
Copy Markdown
Contributor

AppFlow operators validated templated fields in their constructors, which rejected Jinja expressions before Airflow could render them.

This moves the AppFlow source and filter-date validation to execution time so templates are rendered before validation runs. The AppflowBaseOperator exemption is removed from the operator constructor validation list.

related: #70296

Was generative AI tooling used to co-author this PR?
  • [X] Yes (please specify the tool below)

Generated-by: [Codex] following the guidelines


  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {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.

AppFlow operators validate template fields in constructors, so Jinja expressions are rejected before Airflow can render them. Move those checks to execution time so Dags can use templates while keeping the same runtime validation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant