@digitalocean/dots - v1.0.1
    Preparing search index...

    Interface WithManifest_digestItemRequestBuilder

    Builds and executes requests for operations under /v2/registries/{registry_name}/repositories/{repository_name}/digests/{manifest_digest}

    interface WithManifest_digestItemRequestBuilder {
        delete(
            requestConfiguration?: RequestConfiguration<object>,
        ): Promise<void>;
        toDeleteRequestInformation(
            requestConfiguration?: RequestConfiguration<object>,
        ): RequestInformation;
        withUrl(rawUrl: string): WithManifest_digestItemRequestBuilder;
    }

    Hierarchy

    Index

    Methods

    delete toDeleteRequestInformation withUrl

    Methods

    • To delete a container repository manifest by digest in one of your registries, send a DELETE request to/v2/registries/$REGISTRY_NAME/repositories/$REPOSITORY_NAME/digests/$MANIFEST_DIGEST.Note that if your repository name contains / characters, it must beURL-encoded in the request URL. For example, to deleteregistry.digitalocean.com/example/my/repo@sha256:abcd, the path would be/v2/registry/example/repositories/my%2Frepo/digests/sha256:abcd.A successful request will receive a 204 status code with no body in response.This indicates that the request was processed successfully.It is similar to DELETE /v2/registry/$REGISTRY_NAME/repositories/$REPOSITORY_NAME/digests/$MANIFEST_DIGEST and exists for backward compatibility.

      Parameters

      • OptionalrequestConfiguration: RequestConfiguration<object>

        Configuration for the request such as headers, query parameters, and middleware options.

      Returns Promise<void>

      error when the service returns a 401 status code

      error when the service returns a 404 status code

      error when the service returns a 429 status code

      error when the service returns a 500 status code

      error when the service returns a 4XX or 5XX status code

    • To delete a container repository manifest by digest in one of your registries, send a DELETE request to/v2/registries/$REGISTRY_NAME/repositories/$REPOSITORY_NAME/digests/$MANIFEST_DIGEST.Note that if your repository name contains / characters, it must beURL-encoded in the request URL. For example, to deleteregistry.digitalocean.com/example/my/repo@sha256:abcd, the path would be/v2/registry/example/repositories/my%2Frepo/digests/sha256:abcd.A successful request will receive a 204 status code with no body in response.This indicates that the request was processed successfully.It is similar to DELETE /v2/registry/$REGISTRY_NAME/repositories/$REPOSITORY_NAME/digests/$MANIFEST_DIGEST and exists for backward compatibility.

      Parameters

      • OptionalrequestConfiguration: RequestConfiguration<object>

        Configuration for the request such as headers, query parameters, and middleware options.

      Returns RequestInformation

    Settings

    Member Visibility

    On This Page

    Methods