Feature description

Currently the pagination API uses page-based pagination without sorting by time of creation/modification. This leads to incomplete results when iterated over the pages in dynamic systems with multiple modifications happening at the same time when results are fetched.

For example, if during the process of iterating over the pages of environments (api/v1/environment) an additional environment is created, either:

• the new environment will be omitted, or
• a different random environment will be omitted

this is because the environments are sorted by namespace and name. For a more concrete example see the details below.

Instead, one of pagination implementations which guarantees data completeness should be used across conda-store REST API:

• cursor-based pagination
• page pagination with a sort order guaranteeing that newly added records are on the last page (e.g. by date of creation/modification for environments)
• time-based pagination

Value and/or benefit

No randomly missing items (e.g. environments) in paginated replies.

Anything else?

No response