andreahlert opened a new pull request, #61615: URL: https://github.com/apache/airflow/pull/61615
## Summary Adds a `--backend=custom` option to Breeze, allowing users to connect to an external database without spinning up an unnecessary database container. When `custom` is selected: - No database container is started - Users must provide their own connection string via `AIRFLOW__DATABASE__SQL_ALCHEMY_CONN` - A warning is displayed that only officially supported backends are tested - `start-airflow` works normally (unlike `--backend=none`) ### Use case Users running database benchmarks or connecting to remote databases with custom monitoring setups can now use Breeze without creating a dummy container or working around the `--backend=none` limitation. ### Changes - `global_constants.py` - Added `CUSTOM_BACKEND` constant and included it in `ALLOWED_BACKENDS` - `common_options.py` - Updated `--backend` help text to document the custom option - `shell_params.py` - Added `custom` to the list of backends that skip port forwarding - `check_environment.sh` - Added `custom` backend validation (requires `AIRFLOW__DATABASE__SQL_ALCHEMY_CONN`) - `entrypoint_ci.sh` - Added `custom` backend display in initialization info - `backend-custom.yml` - New docker-compose file that sets `BACKEND=custom` without overriding the DB connection Closes: #55886 -- 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]
