Skip to content

Commit e3abeed

Browse files
committed
Clarify tags and deletion of manifests
Signed-off-by: Brandon Mitchell <[email protected]>
1 parent 11b8e3f commit e3abeed

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

spec.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ Several terms are used frequently in this document and warrant basic definitions
7373
- **Object**: one conceptual piece of content stored as blobs with an accompanying manifest. (This was previously described as an "artifact")
7474
- **Descriptor**: a reference that describes the type, metadata and content address of referenced content. Descriptors are defined under the OCI Image Spec <sup>[apdx-5](#appendix)</sup>.
7575
- **Digest**: a unique identifier created from a cryptographic hash of a Blob's content. Digests are defined under the OCI Image Spec <sup>[apdx-3](#appendix)</sup>
76-
- **Tag**: a custom, human-readable manifest identifier
76+
- **Tag**: a custom, human-readable pointer to a manifest. A manifest digest may have zero, one, or many tags referencing it.
7777
- **Subject**: an association from one manifest to another, typically used to attach an artifact to an image.
7878
- **Referrers List**: a list of manifests with a subject relationship to a specified digest. The referrers list is generated with a [query to a registry](#listing-referrers).
7979

@@ -675,6 +675,8 @@ If tag deletion is disabled, the registry MUST respond with either a `400 Bad Re
675675

676676
To delete a tag, perform a `DELETE` request to a path in the following format: `/v2/<name>/manifests/<tag>` <sup>[end-9](#endpoints)</sup>
677677

678+
Once deleted, a `GET` to `/v2/<name>/manifests/<tag>` will return a 404.
679+
678680
##### Deleting Manifests
679681

680682
To delete a manifest, perform a `DELETE` request to a path in the following format: `/v2/<name>/manifests/<digest>` <sup>[end-9](#endpoints)</sup>
@@ -683,6 +685,8 @@ To delete a manifest, perform a `DELETE` request to a path in the following form
683685
Upon success, the registry MUST respond with a `202 Accepted` code.
684686
If the repository does not exist, the response MUST return `404 Not Found`.
685687

688+
Once deleted, a `GET` to `/v2/<name>/manifests/<digest>` and any tag pointing to that digest will return a 404.
689+
686690
When deleting an image manifest that contains a `subject` field, and the [referrers API](#listing-referrers) returns a 404, clients SHOULD:
687691

688692
1. Pull the referrers list using the [referrers tag schema](#referrers-tag-schema).

0 commit comments

Comments
 (0)