action #121099: Add pagination for GET /api/v1/jobs/<job_id:num>/comments - openQA Project (public) - openSUSE Project Management Tool

Actions

action #121099

open

coordination #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/<job_id:num>/comments

Added by kraih about 2 years ago. Updated over 1 year ago.

Status:

New

Priority:

Low

Assignee:

Category:

Feature requests

Target version:

QA (public) - future

Start date:

Due date:

% Done:

Estimated time:

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/<job_id:num>/comments.

Acceptance criteria¶

AC1: API endpoint GET /api/v1/jobs/<job_id:num>/comments has pagination

Suggestions¶

Use limit/offset query parameters and prev/next/first relations in Link headers
If possible use the DBIx::Class features for limit and offset