action #121108
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/workers
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/workers
.
Acceptance criteria¶
- AC1: API endpoint
GET /api/v1/workers
has pagination
Suggestions¶
- Use
limit
/offset
query parameters andprev
/next
/first
relations inLink
headers - If possible use the
DBIx::Class
features forlimit
andoffset
Updated by kraih almost 2 years ago
- Copied from action #121102: Add pagination for GET /api/v1/jobs size:M added
Updated by kraih almost 2 years ago
- Copied to action #121111: Add pagination for GET /api/v1/job_templates added
Updated by okurz almost 2 years ago
- Due date deleted (
2022-12-07) - Start date deleted (
2022-11-22)
Updated by kraih almost 2 years ago
- Target version changed from future to Ready
Lets try to sneak this into the backlog, since there's currently no other API pagination ticket. :)
Updated by openqa_review almost 2 years ago
- Due date set to 2023-03-01
Setting due date based on mean cycle time of SUSE QE Tools
Updated by kraih almost 2 years ago
Updated by kraih almost 2 years ago
- Status changed from In Progress to Feedback