Skip to content

Move DataSync validation after template rendering - #70344

Closed
fat-catTW wants to merge 1 commit into
apache:mainfrom
fat-catTW:fix-datasync-template-field-init
Closed

Move DataSync validation after template rendering#70344
fat-catTW wants to merge 1 commit into
apache:mainfrom
fat-catTW:fix-datasync-template-field-init

Conversation

@fat-catTW

Copy link
Copy Markdown
Contributor

Move DataSyncOperator input validation out of __init__ so templated fields are validated after rendering during execution.

This also removes DataSyncOperator from the operator constructor validation exemptions 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.

@Avcu

Avcu commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Hi @fat-catTW, I created a PR for this earlier and commented in the parent issue:

@shahar1

shahar1 commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Already merged Avcu's solution :)
Feel free to implement for another operator.

@shahar1 shahar1 closed this Jul 24, 2026
@fat-catTW

Copy link
Copy Markdown
Contributor Author

Got it.
Thanks for reviewing. :D

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.

3 participants