Skip to content

Commit

Permalink
Tag pagination
Browse files Browse the repository at this point in the history
Registries must still support the n=100 and last query parameters.
Clients may use the Link header.
When registries cannot return all requested tags, an error must be
returned.

Signed-off-by: Brandon Mitchell <[email protected]>
  • Loading branch information
sudo-bmitch committed Sep 28, 2023
1 parent 6bc8715 commit ac58658
Showing 1 changed file with 9 additions and 2 deletions.
11 changes: 9 additions & 2 deletions spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -526,6 +526,8 @@ In this case, the path will look like the following: `/v2/<name>/tags/list?n=<in
`<name>` is the namespace of the repository, and `<int>` is an integer specifying the number of tags requested.
The response to such a request MAY return fewer than `<int>` results, but only when the total number of tags attached to the repository is less than `<int>`.
Otherwise, the response MUST include `<int>` results.
A `Link` header MAY be included in the response when additional tags are available.
If included, the `Link` header MUST be set according to [RFC5988](https://www.rfc-editor.org/rfc/rfc5988.html) with the Relation Type `rel="next"`.
When `n` is zero, this endpoint MUST return an empty list, and MUST NOT include a `Link` header.
Without the `last` query parameter (described next), the list returned will start at the beginning of the list and include `<int>` results.
As above, the tags MUST be in lexical order.
Expand All @@ -541,6 +543,10 @@ The tags MUST be in lexical order.

When using the `last` query parameter, the `n` parameter is OPTIONAL.

The registry SHOULD support at least `n=100` tags in a single response.
The client SHOULD avoid requesting more than `n=100` tags in a single request.
If the registry is unable to return all tags requested by the client, the registry MUST return a `400 Bad Request` with `TAG_LIMIT_EXCEEDED` error <sup>[code-15](#error-codes)</sup> and include the header `OCI-Tag-Limit: <limit>`, where `<limit>` is the maximum tags per request supported by the registry.

##### Listing Referrers

*Note: this feature was added in distibution-spec 1.1.
Expand Down Expand Up @@ -738,8 +744,8 @@ This endpoint MAY be used for authentication/authorization purposes, but this is
| end-5 | `PATCH` | `/v2/<name>/blobs/uploads/<reference>` | `202` | `404`/`416` |
| end-6 | `PUT` | `/v2/<name>/blobs/uploads/<reference>?digest=<digest>` | `201` | `404`/`400` |
| end-7 | `PUT` | `/v2/<name>/manifests/<reference>` | `201` | `404` |
| end-8a | `GET` | `/v2/<name>/tags/list` | `200` | `404` |
| end-8b | `GET` | `/v2/<name>/tags/list?n=<integer>&last=<integer>` | `200` | `404` |
| end-8a | `GET` | `/v2/<name>/tags/list` | `200` | `404`/`400` |
| end-8b | `GET` | `/v2/<name>/tags/list?n=<integer>&last=<integer>` | `200` | `404`/`400` |
| end-9 | `DELETE` | `/v2/<name>/manifests/<reference>` | `202` | `404`/`400`/`405` |
| end-10 | `DELETE` | `/v2/<name>/blobs/<digest>` | `202` | `404`/`405` |
| end-11 | `POST` | `/v2/<name>/blobs/uploads/?mount=<digest>&from=<other_name>` | `201` | `404` |
Expand Down Expand Up @@ -787,6 +793,7 @@ The `code` field MUST be one of the following:
| code-12 | `DENIED` | requested access to the resource is denied |
| code-13 | `UNSUPPORTED` | the operation is unsupported |
| code-14 | `TOOMANYREQUESTS` | too many requests |
| code-15 | `TAG_LIMIT_EXCEEDED` | too many tags were requested |

#### Warnings

Expand Down

0 comments on commit ac58658

Please sign in to comment.