opencontainers
Clarify manifest deletion as sync or async
In the section around deleting manifests, the following statements are made:
Upon success, the registry MUST respond with a
202 Acceptedcode.
Once deleted, a
GETto/v2/<name>/manifests/<digest>and any tag pointing to that digest will return a 404.
A 202 Accepted is defined as:
request has been accepted for processing, but processing has not been completed or may not have started
Additionally, in the conformance tests, after performing a delete call, it is valid to receive back a 404 OR a 200 when immediately trying to GET that same manifest.
By this, it seems that it is perfectly fine for a registry implementation to delete manifests via an "eventually consistent" process, though it would be reasonable to expect this to happen quickly. Is this a proper interpretation?
