-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Closed
Closed
Copy link
Labels
area:dev-envCI, pre-commit, pylint and other changes that do not change the behavior of the final codeCI, pre-commit, pylint and other changes that do not change the behavior of the final codekind:featureFeature RequestsFeature Requestsneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yet
Description
Description
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.
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
- I agree to follow this project's 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 codeCI, pre-commit, pylint and other changes that do not change the behavior of the final codekind:featureFeature RequestsFeature Requestsneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yet
