{{ message }}
Speed up breeze start-airflow by skipping a redundant CLI call - #73174
Open
Andrushika wants to merge 1 commit into
Open
Andrushika wants to merge 1 commit into
Andrushika wants to merge 1 commit into
Conversation
check_environment.sh only needs the auth manager class path to decide whether to create FAB users. breeze always exports AIRFLOW__CORE__AUTH_MANAGER, and env vars are first in Airflow's config lookup, so the CLI would print that same value after a full Airflow startup. Read the env var directly and keep the CLI as a fallback.
Andrushika
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
potiuk
as code owners
September 15, 2026 09:56
Andrushika
marked this pull request as draft
September 15, 2026 11:18
Andrushika
marked this pull request as ready for review
September 15, 2026 11:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
check_environment.shrunsairflow config get-value core auth_manageron everybreeze start-airflowto see if it should create the FAB admin user. That starts a full Airflow process just to print one value. breeze already setsAIRFLOW__CORE__AUTH_MANAGER, and env vars win in config lookup, so the CLI only echoes it back. On my machine that call takes 2.2 to 2.6s each start.What
Read the env var in the shell first. Fall back to the CLI only when it is empty, which keeps the Airflow 2.x path working.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Fable 5.1) following the guidelines