Skip to content

Improve error message when using start-airflow with --backend none in Breeze #52315

@kyungjunleeme

Description

@kyungjunleeme

Description

related https://apache-airflow.slack.com/archives/CQ9QHSFQX/p1750917889606339?thread_ts=1750915462.814829&cid=CQ9QHSFQX

Problem

Currently, when users run breeze --backend none and attempt to use start-airflow, it results in a cryptic error or unexpected behavior. This can be confusing, especially for newcomers who might not realize that the none backend is intended for non-DB tests and is not compatible with start-airflow.

Image

Proposed Improvement

Improve the developer experience by adding a clearer error or warning message in start-airflow when the backend is set to none.

Use case/motivation

No response

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

Labels

area:dev-envCI, pre-commit, pylint and other changes that do not change the behavior of the final codekind:featureFeature Requestsneeds-triagelabel for new issues that we didn't triage yet

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions