Clarify that manifests can only be deleted by digest
Signed-off-by: Stephen J Day <stephen.day@docker.com>master
							parent
							
								
									97ca39d26d
								
							
						
					
					
						commit
						c54adb667f
					
				|  | @ -717,7 +717,7 @@ A list of methods and URIs are covered in the table below: | |||
| | GET | `/v2/<name>/tags/list` | Tags | Fetch the tags under the repository identified by `name`. | | ||||
| | GET | `/v2/<name>/manifests/<reference>` | Manifest | Fetch the manifest identified by `name` and `reference` where `reference` can be a tag or digest. | | ||||
| | PUT | `/v2/<name>/manifests/<reference>` | Manifest | Put the manifest identified by `name` and `reference` where `reference` can be a tag or digest. | | ||||
| | DELETE | `/v2/<name>/manifests/<reference>` | Manifest | Delete the manifest identified by `name` and `reference` where `reference` can be a tag or digest. | | ||||
| | DELETE | `/v2/<name>/manifests/<reference>` | Manifest | Delete the manifest identified by `name` and `reference`. Note that a manifest can _only_ be deleted by `digest`. | | ||||
| | GET | `/v2/<name>/blobs/<digest>` | Blob | Retrieve the blob from the registry identified by `digest`. A `HEAD` request can also be issued to this endpoint to obtain resource information without receiving all data. | | ||||
| | POST | `/v2/<name>/blobs/uploads/` | Intiate Blob Upload | Initiate a resumable blob upload. If successful, an upload location will be provided to complete the upload. Optionally, if the `digest` parameter is present, the request body will be used to complete the upload in a single request. | | ||||
| | GET | `/v2/<name>/blobs/uploads/<uuid>` | Blob Upload | Retrieve status of upload identified by `uuid`. The primary purpose of this endpoint is to resolve the current status of a resumable upload. | | ||||
|  | @ -1324,7 +1324,7 @@ The error codes that may be included in the response body are enumerated below: | |||
| 
 | ||||
| #### DELETE Manifest | ||||
| 
 | ||||
| Delete the manifest identified by `name` and `reference` where `reference` can be a tag or digest. | ||||
| Delete the manifest identified by `name` and `reference`. Note that a manifest can _only_ be deleted by `digest`. | ||||
| 
 | ||||
| 
 | ||||
| 
 | ||||
|  | @ -1361,7 +1361,7 @@ The following parameters should be specified on the request: | |||
| 
 | ||||
| 
 | ||||
| 
 | ||||
| ###### On Failure: Invalid Name or Tag | ||||
| ###### On Failure: Invalid Name or Reference | ||||
| 
 | ||||
| ``` | ||||
| 400 Bad Request | ||||
|  | @ -1379,7 +1379,7 @@ Content-Type: application/json; charset=utf-8 | |||
| } | ||||
| ``` | ||||
| 
 | ||||
| The specified `name` or `tag` were invalid and the delete was unable to proceed. | ||||
| The specified `name` or `reference` were invalid and the delete was unable to proceed. | ||||
| 
 | ||||
| 
 | ||||
| 
 | ||||
|  | @ -1449,7 +1449,7 @@ Content-Type: application/json; charset=utf-8 | |||
| } | ||||
| ``` | ||||
| 
 | ||||
| The specified `name` or `tag` are unknown to the registry and the delete was unable to proceed. Clients can assume the manifest was already deleted if this response is returned. | ||||
| The specified `name` or `reference` are unknown to the registry and the delete was unable to proceed. Clients can assume the manifest was already deleted if this response is returned. | ||||
| 
 | ||||
| 
 | ||||
| 
 | ||||
|  |  | |||
|  | @ -639,7 +639,7 @@ var routeDescriptors = []RouteDescriptor{ | |||
| 			}, | ||||
| 			{ | ||||
| 				Method:      "DELETE", | ||||
| 				Description: "Delete the manifest identified by `name` and `reference` where `reference` can be a tag or digest.", | ||||
| 				Description: "Delete the manifest identified by `name` and `reference`. Note that a manifest can _only_ be deleted by `digest`.", | ||||
| 				Requests: []RequestDescriptor{ | ||||
| 					{ | ||||
| 						Headers: []ParameterDescriptor{ | ||||
|  | @ -657,8 +657,8 @@ var routeDescriptors = []RouteDescriptor{ | |||
| 						}, | ||||
| 						Failures: []ResponseDescriptor{ | ||||
| 							{ | ||||
| 								Name:        "Invalid Name or Tag", | ||||
| 								Description: "The specified `name` or `tag` were invalid and the delete was unable to proceed.", | ||||
| 								Name:        "Invalid Name or Reference", | ||||
| 								Description: "The specified `name` or `reference` were invalid and the delete was unable to proceed.", | ||||
| 								StatusCode:  http.StatusBadRequest, | ||||
| 								ErrorCodes: []ErrorCode{ | ||||
| 									ErrorCodeNameInvalid, | ||||
|  | @ -690,7 +690,7 @@ var routeDescriptors = []RouteDescriptor{ | |||
| 							}, | ||||
| 							{ | ||||
| 								Name:        "Unknown Manifest", | ||||
| 								Description: "The specified `name` or `tag` are unknown to the registry and the delete was unable to proceed. Clients can assume the manifest was already deleted if this response is returned.", | ||||
| 								Description: "The specified `name` or `reference` are unknown to the registry and the delete was unable to proceed. Clients can assume the manifest was already deleted if this response is returned.", | ||||
| 								StatusCode:  http.StatusNotFound, | ||||
| 								ErrorCodes: []ErrorCode{ | ||||
| 									ErrorCodeNameUnknown, | ||||
|  |  | |||
		Loading…
	
		Reference in New Issue