Project

General

Profile

action #121099

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 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:
medium

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

Related issues

Copied from openQA Project - action #121048: Add pagination for GET /api/v1/bugsResolved2022-11-22

Copied to openQA Project - action #121102: Add pagination for GET /api/v1/jobs size:MResolved

History

#1 Updated by kraih 2 months ago

  • Copied from action #121048: Add pagination for GET /api/v1/bugs added

#2 Updated by kraih 2 months ago

  • Copied to action #121102: Add pagination for GET /api/v1/jobs size:M added

#3 Updated by kraih 2 months ago

  • Assignee deleted (kraih)

#4 Updated by okurz about 2 months ago

  • Due date deleted (2022-12-07)
  • Start date deleted (2022-11-22)

Also available in: Atom PDF