[Explore]: How to implement pagination with the current approach?

[c0d1ngm0nk3y]

Background

Most (if not even all) cf list endpoints (e.g. /v3/apps) have the possibility for pagination by using the parameters page and per_page.

But when calling List on k8s there is no way to to implement such a pagination with the possibility to jump to arbitrary pages directly and efficiently.

How should/could this be done?

Acceptance Criteria

Implementation of pagination for an existing endpoint.

Timebox

No timebox since it has to be solved to be api compatible.

Dev Notes

Just listing everything and returning the requested page to the user, is not really an option because this would scale very poorly.

[c0d1ngm0nk3y]

github-project-automation bot moved this to 🧊 Icebox in Korifi - Backlog

@danail-branekov What does that mean?

[danail-branekov]

@danail-branekov What does that mean?

Whenever someone creates a new issue, the automation puts it into the Icebox bucket of the Korifi backlog. This is the place where we keep things to do that we have not prioritised yet