Regenerate airflowctl datamodels from this branch's API spec - #71094
Draft
Lee-W wants to merge 1 commit into
Draft
Regenerate airflowctl datamodels from this branch's API spec#71094Lee-W wants to merge 1 commit into
Lee-W wants to merge 1 commit into
Conversation
The test-to-stable sync (apache#67294) copied airflowctl's generated datamodels from main, so they describe Airflow 3.3's API while this branch ships core 3.2.1. Two consequences, both red once CI started running here: - generate-airflowctl-datamodels regenerates from ../airflow-core/src/airflow/api_fastapi and fails on any drift, so Static checks could never pass - the models required is_backfillable and timetable_periodic, which apache#64644 added in 3.3.0, so every single-object Dag response failed validation against this branch's own PROD image: ValidationError: 2 validation errors for DAGResponse is_backfillable Field required timetable_periodic Field required Run the hook to bring the models back in line with the spec on this branch. This drops 14 model classes that no airflowctl code or test references, plus the 3.3-only fields above. Note RELEASE_NOTES.rst credits "Add ``is_backfillable`` property to DAG API responses (apache#64644)" to airflowctl 0.1.5, but apache#64644 touches only airflow-core -- that line is sync noise, not a client feature.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The test-to-stable sync (#67294) copied airflowctl's generated datamodels from main, so they describe Airflow 3.3's API while this branch ships core 3.2.1. Two consequences, both red once CI started running here (#70724):
generate-airflowctl-datamodelsregenerates from../airflow-core/src/airflow/api_fastapiand fails on any drift, so Static checks could never passis_backfillableandtimetable_periodic, which Addis_backfillableproperty to DAG API responses #64644 added in 3.3.0, so every single-object Dag response failed validation against this branch's own PROD image:This runs the hook to bring the models back in line with the spec on this branch. It drops 14 model classes that no airflowctl code or test references, plus the 3.3-only fields above.
Note
RELEASE_NOTES.rstcredits "Addis_backfillableproperty to DAG API responses (#64644)" to airflowctl 0.1.5, but #64644 touches only airflow-core — that line is sync noise, not a client feature.Split out of #70724 so that PR stays workflow-only.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Opus 5 following the guidelines