Asquator opened a new issue, #55886: URL: https://github.com/apache/airflow/issues/55886
### Description Currently we have these lines: https://github.com/apache/airflow/blob/9bfa389e10087c4caeffdd0581af109457ad05e8/scripts/in_container/check_environment.sh#L66-L71 That fails Breeze if `--backend=none` is specified. In some cases a user would like to provide his own database backend by overriding `AIRFLOW__DATABASE__SQL_ALCHEMY_CONN`. As `none` is illegal here, we have to spin up another container / provide `sqlite` as a dummy value. Sometimes we don't want to run the DB as a container (say we need a remote DB with more resources), so it's desirable to allow custom backends whether by allowing `--backend=none`, or adding `--backend=custom` option, with an indicative warning that only official backends are supported (this is my preferred option). What do you think about it? ### Use case/motivation I'm doing database benchmarks to see how different task queueing strategies perform, and I spin up an external PostgreSQL DB with a monitoring system of its own. I want Breeze to connect to it without creating a useless container. ### Related issues _No response_ ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
