Description
When a user goes to the /dags screen, they are first greeted by the UI skeleton, with some loading indicators and no dags. This is because the FastAPI server is requesting authorisation for each dag object individually. For deployments where there are lots of dags this takes a long time, so users can be stuck waiting for the dags screen to be populated for long periods of time (1 minute+ in some cases).
Use case/motivation
In order to make the /dags and other aggregate list view screens more usable, asynchronously load each dag onto the screen in a list while the authorisation is confirming access for the remaining dags. This allows users to get some information about the system state before the entire UI has loaded.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
Description
When a user goes to the
/dagsscreen, they are first greeted by the UI skeleton, with some loading indicators and no dags. This is because the FastAPI server is requesting authorisation for each dag object individually. For deployments where there are lots of dags this takes a long time, so users can be stuck waiting for the dags screen to be populated for long periods of time (1 minute+ in some cases).Use case/motivation
In order to make the
/dagsand other aggregate list view screens more usable, asynchronously load each dag onto the screen in a list while the authorisation is confirming access for the remaining dags. This allows users to get some information about the system state before the entire UI has loaded.Related issues
No response
Are you willing to submit a PR?
Code of Conduct