Skip to content

Expose build constraints configuration in Breeze#69082

Closed
nailo2c wants to merge 1 commit into
apache:mainfrom
nailo2c:feat-54394-breeze-build-constraints
Closed

Expose build constraints configuration in Breeze#69082
nailo2c wants to merge 1 commit into
apache:mainfrom
nailo2c:feat-54394-breeze-build-constraints

Conversation

@nailo2c

@nailo2c nailo2c commented Jun 27, 2026

Copy link
Copy Markdown
Contributor

This is PR3 of the split replacement for #65511.

It exposes an explicit Breeze path for build constraints without changing the default constraints behaviour:

  • adds --airflow-build-constraints-location / AIRFLOW_BUILD_CONSTRAINTS_LOCATION
  • forwards the value to breeze ci-image build and breeze prod-image build as a Docker build arg
  • forwards the value to shell-based workflows as an environment variable
  • regenerates the affected Breeze command images and command hashes

Covered commands:

  • breeze ci-image build
  • breeze prod-image build
  • breeze shell
  • breeze start-airflow
  • breeze release-management install-provider-distributions
  • breeze release-management verify-provider-distributions

This intentionally does not add automatic constraints branch inference or default published build constraints. That remains deferred to PR4.

Split order:

  1. Generate and publish build constraints #68937
  2. Support explicit build constraints in install flows #68962
  3. this PR
  4. PR4

This PR is draft until the earlier split PRs are ready/merged.

Validation:

  • breeze setup regenerate-command-images --check-only
  • breeze setup check-all-params-in-groups
  • breeze --answer n run pytest dev/breeze/tests/test_build_constraints_breeze_options.py dev/breeze/tests/test_shell_params.py -xvs
  • PATH="/Users/aaron.chen/.local/bin:$PATH" prek run --from-ref upstream/main --stage pre-commit
  • PATH="/Users/aaron.chen/.local/bin:$PATH" prek run --from-ref upstream/main --stage manual
  • breeze ci selective-check --commit-ref HEAD

related: #54394


Was generative AI tooling used to co-author this PR?
  • Yes — Codex (GPT-5)

Generated-by: Codex (GPT-5) following the guidelines

Breeze needs an explicit way to pass build constraints through image builds and shell-based release workflows before automatic published-constraints defaults are enabled.
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