Project

General

Profile

Actions
Copy link

Support #20144

open

Make api pagination optional

Added by Dinar Valeev almost 8 years ago. Updated almost 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Triaged:
Fixed in Releases:
Found in Releases:

Description

by default foreman paginate API by entries_per_page setting, while having in API documentation "GET /api/compute_resources/:compute_resource_id/images " page
optional

paginate results

Validations:

Must be String

Made me think pagination is really optional.

IMO if result is to big for compute to be processed a program/user can request it paginated by specifying per_page/page. Otherwise API should return ALL results

Actions
Copy link
 #1

Updated by Daniel Lobato Garcia almost 8 years ago

  • Tracker changed from Feature to Support
  • Subject changed from make api pagination optional to Make api pagination optional

I would say we already do this to some degree:

If the result is bigger than 20 - our default per_page (can be changed on Administer > Settings in Foreman), the output is served paginated.

If you feel that the default is too small (I don't think it is, for some pages, especially Katello related objects which have to query external APIs), you can either change it, or request per_page = 9999999999.

I'm changing the type of the issue to "Support" for the time being, as I'm not quite sure what would you like us to implement here :) Disabling the pagination is unlikely to be implemented at this point, for API v3 I would rather move to GraphQL which should allow anyone to do this.

Actions
Copy link

Also available in: Atom PDF