Documentation ¶
Index ¶
- func CopyArtifactMiddleware() func(http.Handler) http.Handler
- func HeadBlobMiddleware() func(http.Handler) http.Handler
- func PatchBlobUploadMiddleware() func(http.Handler) http.Handler
- func PostInitiateBlobUploadMiddleware() func(http.Handler) http.Handler
- func PutBlobUploadMiddleware() func(http.Handler) http.Handler
- func PutManifestMiddleware() func(http.Handler) http.Handler
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func CopyArtifactMiddleware ¶
CopyArtifactMiddleware middleware to sync the missing associations for the project
func HeadBlobMiddleware ¶
HeadBlobMiddleware intercept the head blob request
func PatchBlobUploadMiddleware ¶
PatchBlobUploadMiddleware middleware to record the accepted blob size for stream blob upload
func PostInitiateBlobUploadMiddleware ¶
PostInitiateBlobUploadMiddleware middleware to add blob to project after mount blob success
func PutBlobUploadMiddleware ¶
PutBlobUploadMiddleware middleware is to update the blob status according to the different situation before the request passed into proxy(distribution). And it creates Blob and ProjectBlob after PUT /v2/<name>/blobs/uploads/<session_id>?digest=<digest> success - http.StatusCreated Why to use the middleware to handle blob status? 1, As Put blob will always happen after head blob gets a 404, but the 404 could be caused by blob status is deleting, which is marked by GC. 2, It has to deal with the concurrence blob push.
func PutManifestMiddleware ¶
PutManifestMiddleware middleware middleware is to update the manifest status according to the different situation before the request passed into proxy(distribution). and it creates Blobs for the foreign layers and associate them with the project, updates the content type of the Blobs which already exist, create Blob for the manifest, associate all Blobs with the manifest after PUT /v2/<name>/manifests/<reference> success.
Types ¶
This section is empty.