Project

General

Profile

Actions

action #121048

closed

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/bugs

Added by kraih over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2022-11-22
Due date:
% Done:

0%

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/bugs.

Acceptance criteria

  • AC1: API endpoint GET /api/v1/bugs 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 2 (1 open1 closed)

Copied from openQA Project - action #120841: Add pagination for GET /api/v1/assets size:MResolvedkraih2022-11-22

Actions
Copied to openQA Project - action #121099: Add pagination for GET /api/v1/jobs/<job_id:num>/commentsNew

Actions
Actions

Also available in: Atom PDF