Mirror writes to database: Blob DELETE Handler
Context
This issue is meant to investigate steps which are required to mirror metadata writes generated from calls the Blob DELETE Handler.
Affected Route(s)
DELETE /v2/<name>/blobs/<digest>
Detailed Handler Operations
- Instantiate a
distribution.BlobStore
, the concrete type is astoreage.linkedBlobStore
- Call
storeage.linkedBlobStore.Delete(ctx, tagHandler.Tag)
- Return error if deletion is not supported
- call
storeage.linkedBlobStore.blobAccessController.Clear(ctx, digest.Digest)
, concrete type is (probably)storage.linkedBlobStatter
- call driver.StorageDriver.Delete on
blobLinkPath
(<root>/v2/repositories/<name>/_layers/<algorithm>/<hex digest>/link
), ignoring driver.PathNotFoundError
- call driver.StorageDriver.Delete on
- call
http.ResponseWriter.WriteHeader(http.StatusAccepted)
Edited by Hayley Swimelar