vatsrahul1001 opened a new pull request, #68659: URL: https://github.com/apache/airflow/pull/68659
### Problem The PROD image verify (`docker-tests/.../test_prod_image.py::test_required_providers_are_installed`) fails on release branches (e.g. `v3-3-test`) reporting that `opensearch` is missing from the image, while `main` passes. Root cause: #65374 added `opensearch` to `prod_image_installed_providers.txt` (so the verify now asserts it is installed) but did **not** add it to the default image extras. That makes `opensearch` the only required provider that is **neither a default extra nor a bundled core dependency** — so its only path into the image was being built from source. On a release branch, the source provider build skips already-released providers (the `providers-opensearch/<version>` final tag exists), so `opensearch` is the single required provider with no fallback and the verify fails. `main` passes only because its dev-mode build compiles every provider from source in-place regardless of tags. Every other required provider survives the release-branch skip because it is either in the default extras (backfilled from PyPI) or a bundled core dependency. ### Fix Add `opensearch` to the default PROD image extras (`Dockerfile` `ARG AIRFLOW_EXTRAS`), and let the `check-extras-order` hook propagate it into `global_constants.py` (`DEFAULT_EXTRAS`) and `docker-stack-docs/build-arg-ref.rst`. The breeze command-output image for `prod-image build` is regenerated accordingly. This backfills `opensearch` from PyPI the same way every other required provider is installed, making the PROD image consistent across dev and release builds. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 4.8) Generated-by: Claude Code (Opus 4.8) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
