Make param validation consistent for DAG validation and triggering #34248
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.
This PR adjusts the DAG level Params validation to the validation also used during triggering and DAG constructor.
It resolves the problem reported in #34227 that params with a value of
None
are leading to invalid/unparsable DAGs after upgrade to Airflow 2.7.1 as a side effect of #33141 - reason is that the validation previously checked forhas_value
assuming that the schema also defines a required field.How to test:
closes: #34227
related: #31299, #31301