Allow configuring the default landing page - #70754
Open
dsuhinin wants to merge 5 commits into
Open
Conversation
dsuhinin
requested review from
bbovenzi,
bugraoz93,
choo121600,
ephraimbuddy,
guan404ming,
henry3260,
jason810496,
pierrejeambrun,
rawwar,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
July 30, 2026 10:38
boring-cyborg
Bot
added
area:API
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.
Some deployments barely use the Home dashboard — people open Airflow and immediately click through to the Dag list, every single time. This adds a small knob so the root URL can open the page they actually work in.
New
[api] default_landing_pageconfig option, defaulting tohome— nothing changes unless you opt in. Setting it todagsmakes/redirect to the Dag list, while the Home dashboard stays reachable at/home, so nobody loses anything. The value is exposed through the existing UI config endpoint, and a tinyLandingPagecomponent picks between rendering the dashboard and redirecting, so there's no server-side routing involved.Tests cover both the config endpoint exposing the new option and the landing component's behaviour for each value.