fix: add /applications/grouped endpoint to reduce initial page load API calls#3034
Merged
Conversation
Merged
3 tasks
…ked around defaults while still supporting server side pagination
grudra7714
approved these changes
May 20, 2026
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
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.
PR Checklist
Summary
Fixes the N+1 API call problem on the app list page. Each namespace had its own paginated table, causing one HTTP call per namespace on initial load. This adds a single endpoint that fans out server-side and returns all namespaces in one response.
Pairs with epinio/ui#580.
Occurred changes and/or fixed issues
GET /api/v1/applications/groupedreturningmap[namespace]PaginatedResponse[App]ListPaginatedByNamespaceininternal/application/usingerrgroupto fan outListPaginatedcalls concurrently across all namespacesrouter.goand addedAllAppsGroupedaction toauth/actions.yamlTechnical notes summary
Latency is now bounded by the slowest namespace rather than the sum of all namespaces. Auth filtering (
auth.FilterResources) is applied per namespace in the handler before building the response, consistent with other list endpoints.Areas or cases that should be tested
Areas which could experience regressions
/namespaces/:ns/applications)