Actions
action #121102
closedcoordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes
coordination #92854: [epic] limit overload of openQA webUI by heavy requests
action #97190: Limit size of initial requests everywhere, e.g. /, /tests, etc., over webUI and API
action #119428: Ensure users can get all the data for limited queries, e.g. with pagination
Add pagination for GET /api/v1/jobs size:M
Description
Motivation¶
Proper pagination is planned for every query and API route in #119428. After #120841 has been implemented we now have a prototype to replicate. So this needs to be done for GET /api/v1/jobs.
Acceptance criteria¶
- AC1: API endpoint
GET /api/v1/jobshas pagination
Suggestions¶
- Use
limit/offsetquery parameters andprev/next/firstrelations inLinkheaders - If possible use the
DBIx::Classfeatures forlimitandoffset - See official documentation (https://docs.mojolicious.org/Mojolicious/Plugin/DefaultHelpers, https://docs.mojolicious.org/Mojolicious/Validator/Validation, https://metacpan.org/pod/DBIx::Class::ResultSet)
- Use helper added in https://github.com/os-autoinst/openQA/pull/4934 for pagination headers
Actions