mirror of
https://github.com/kubernetes-sigs/descheduler.git
synced 2026-01-28 14:41:10 +01:00
Update vendor dir for kube 1.9 rebase.
This commit is contained in:
Avesh Agarwal
682
vendor/github.com/docker/distribution/docs/spec/api.md
generated
vendored
682
vendor/github.com/docker/distribution/docs/spec/api.md
generated
vendored
@@ -1,12 +1,8 @@
|
||||
<!--[metadata]>
|
||||
+++
|
||||
title = "HTTP API V2"
|
||||
description = "Specification for the Registry API."
|
||||
keywords = ["registry, on-prem, images, tags, repository, distribution, api, advanced"]
|
||||
[menu.main]
|
||||
parent="smn_registry_ref"
|
||||
+++
|
||||
<![end-metadata]-->
|
||||
---
|
||||
title: "HTTP API V2"
|
||||
description: "Specification for the Registry API."
|
||||
keywords: ["registry, on-prem, images, tags, repository, distribution, api, advanced"]
|
||||
---
|
||||
|
||||
# Docker Registry HTTP API V2
|
||||
|
||||
@@ -126,6 +122,13 @@ reference and shouldn't be used outside the specification other than to
|
||||
identify a set of modifications.
|
||||
|
||||
<dl>
|
||||
<dt>l</dt>
|
||||
<dd>
|
||||
<ul>
|
||||
<li>Document TOOMANYREQUESTS error code.</li>
|
||||
</ul>
|
||||
</dd>
|
||||
|
||||
<dt>k</dt>
|
||||
<dd>
|
||||
<ul>
|
||||
@@ -241,7 +244,7 @@ enforce this. The rules for a repository name are as follows:
|
||||
must match the regular expression `[a-z0-9]+(?:[._-][a-z0-9]+)*`.
|
||||
2. If a repository name has two or more path components, they must be
|
||||
separated by a forward slash ("/").
|
||||
3. The total length of a repository name, including slashes, must be less the
|
||||
3. The total length of a repository name, including slashes, must be less than
|
||||
256 characters.
|
||||
|
||||
These name requirements _only_ apply to the registry API and should accept a
|
||||
@@ -618,26 +621,6 @@ The "digest" parameter must be included with the PUT request. Please see the
|
||||
[_Completed Upload_](#completed-upload) section for details on the parameters
|
||||
and expected responses.
|
||||
|
||||
Additionally, the upload can be completed with a single `POST` request to
|
||||
the uploads endpoint, including the "size" and "digest" parameters:
|
||||
|
||||
```
|
||||
POST /v2/<name>/blobs/uploads/?digest=<digest>
|
||||
Content-Length: <size of layer>
|
||||
Content-Type: application/octet-stream
|
||||
|
||||
<Layer Binary Data>
|
||||
```
|
||||
|
||||
On the registry service, this should allocate a download, accept and verify
|
||||
the data and return the same response as the final chunk of an upload. If the
|
||||
POST request fails collecting the data in any way, the registry should attempt
|
||||
to return an error response to the client with the `Location` header providing
|
||||
a place to continue the download.
|
||||
|
||||
The single `POST` method is provided for convenience and most clients should
|
||||
implement `POST` + `PUT` to support reliable resume of uploads.
|
||||
|
||||
##### Chunked Upload
|
||||
|
||||
To carry out an upload of a chunk, the client can specify a range header and
|
||||
@@ -693,7 +676,7 @@ the upload will not be considered complete. The format for the final chunk
|
||||
will be as follows:
|
||||
|
||||
```
|
||||
PUT /v2/<name>/blob/uploads/<uuid>?digest=<digest>
|
||||
PUT /v2/<name>/blobs/uploads/<uuid>?digest=<digest>
|
||||
Content-Length: <size of chunk>
|
||||
Content-Range: <start of range>-<end of range>
|
||||
Content-Type: application/octet-stream
|
||||
@@ -726,7 +709,7 @@ the uploaded blob data.
|
||||
###### Digest Parameter
|
||||
|
||||
The "digest" parameter is designed as an opaque parameter to support
|
||||
verification of a successful transfer. For example, a HTTP URI parameter
|
||||
verification of a successful transfer. For example, an HTTP URI parameter
|
||||
might be as follows:
|
||||
|
||||
```
|
||||
@@ -812,7 +795,7 @@ Note that the upload url will not be available forever. If the upload uuid is
|
||||
unknown to the registry, a `404 Not Found` response will be returned and the
|
||||
client must restart the upload process.
|
||||
|
||||
### Deleting a Layer
|
||||
#### Deleting a Layer
|
||||
|
||||
A layer may be deleted from the registry via its `name` and `digest`. A
|
||||
delete may be issued with the following request format:
|
||||
@@ -1256,6 +1239,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Tags
|
||||
@@ -1431,6 +1451,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
##### Tags Paginated
|
||||
|
||||
```
|
||||
@@ -1593,6 +1650,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Manifest
|
||||
@@ -1805,6 +1899,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
|
||||
#### PUT Manifest
|
||||
|
||||
@@ -2017,6 +2148,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
###### On Failure: Missing Layer(s)
|
||||
|
||||
```
|
||||
@@ -2249,6 +2417,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
###### On Failure: Unknown Manifest
|
||||
|
||||
```
|
||||
@@ -2549,6 +2754,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
##### Fetch Blob Part
|
||||
|
||||
```
|
||||
@@ -2782,6 +3024,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
|
||||
#### DELETE Blob
|
||||
|
||||
@@ -3023,6 +3302,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Initiate Blob Upload
|
||||
@@ -3236,6 +3552,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
##### Initiate Resumable Blob Upload
|
||||
|
||||
```
|
||||
@@ -3416,6 +3769,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
##### Mount Blob
|
||||
|
||||
```
|
||||
@@ -3614,6 +4004,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Blob Upload
|
||||
@@ -3846,6 +4273,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
|
||||
#### PATCH Blob Upload
|
||||
|
||||
@@ -4077,6 +4541,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
##### Chunked upload
|
||||
|
||||
```
|
||||
@@ -4316,6 +4817,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
|
||||
#### PUT Blob Upload
|
||||
|
||||
@@ -4550,6 +5088,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
|
||||
#### DELETE Blob Upload
|
||||
|
||||
@@ -4772,6 +5347,43 @@ The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|
||||
|
||||
###### On Failure: Too Many Requests
|
||||
|
||||
```
|
||||
429 Too Many Requests
|
||||
Content-Length: <length>
|
||||
Content-Type: application/json; charset=utf-8
|
||||
|
||||
{
|
||||
"errors:" [
|
||||
{
|
||||
"code": <error code>,
|
||||
"message": "<error message>",
|
||||
"detail": ...
|
||||
},
|
||||
...
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The client made too many requests within a time interval.
|
||||
|
||||
The following headers will be returned on the response:
|
||||
|
||||
|Name|Description|
|
||||
|----|-----------|
|
||||
|`Content-Length`|Length of the JSON response body.|
|
||||
|
||||
|
||||
|
||||
The error codes that may be included in the response body are enumerated below:
|
||||
|
||||
|Code|Message|Description|
|
||||
|----|-------|-----------|
|
||||
| `TOOMANYREQUESTS` | too many requests | Returned when a client attempts to contact a service too many times |
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Catalog
|
||||
@@ -4785,13 +5397,13 @@ List a set of available repositories in the local registry cluster. Does not pro
|
||||
Retrieve a sorted, json list of repositories available in the registry.
|
||||
|
||||
|
||||
##### Catalog Fetch Complete
|
||||
##### Catalog Fetch
|
||||
|
||||
```
|
||||
GET /v2/_catalog
|
||||
```
|
||||
|
||||
Request an unabridged list of repositories available.
|
||||
Request an unabridged list of repositories available. The implementation may impose a maximum limit and return a partial set with pagination links.
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user