Expose build constraints configuration in Breeze#69082
Closed
nailo2c wants to merge 1 commit into
Closed
Conversation
Breeze needs an explicit way to pass build constraints through image builds and shell-based release workflows before automatic published-constraints defaults are enabled.
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
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 is PR3 of the split replacement for #65511.
It exposes an explicit Breeze path for build constraints without changing the default constraints behaviour:
--airflow-build-constraints-location/AIRFLOW_BUILD_CONSTRAINTS_LOCATIONbreeze ci-image buildandbreeze prod-image buildas a Docker build argCovered commands:
breeze ci-image buildbreeze prod-image buildbreeze shellbreeze start-airflowbreeze release-management install-provider-distributionsbreeze release-management verify-provider-distributionsThis intentionally does not add automatic constraints branch inference or default published build constraints. That remains deferred to PR4.
Split order:
This PR is draft until the earlier split PRs are ready/merged.
Validation:
breeze setup regenerate-command-images --check-onlybreeze setup check-all-params-in-groupsbreeze --answer n run pytest dev/breeze/tests/test_build_constraints_breeze_options.py dev/breeze/tests/test_shell_params.py -xvsPATH="/Users/aaron.chen/.local/bin:$PATH" prek run --from-ref upstream/main --stage pre-commitPATH="/Users/aaron.chen/.local/bin:$PATH" prek run --from-ref upstream/main --stage manualbreeze ci selective-check --commit-ref HEADrelated: #54394
Was generative AI tooling used to co-author this PR?
Generated-by: Codex (GPT-5) following the guidelines