repository_manifests

Creates, updates, deletes, gets or lists a repository_manifests resource.

Overview

Name	repository_manifests
Type	Resource
Id	digitalocean.container_registry.repository_manifests

Fields

The following fields are returned by SELECT queries:

registries_list_repository_manifests

The response body will be a JSON object with a key of manifests. This will be set to an array containing objects each representing a manifest.

Name	Datatype	Description
registry_name	string	The name of the container registry. (example: example)
blobs	array	All blobs associated with this manifest
compressed_size_bytes	integer	The compressed size of the manifest in bytes.
digest	string	The manifest digest (example: sha256:cb8a924afdf0229ef7515d9e5b3024e23b3eb03ddbba287f4a19c6ac90b8d221)
repository	string	The name of the repository. (example: repo-1)
size_bytes	integer	The uncompressed size of the manifest in bytes (this size is calculated asynchronously so it may not be immediately available).
tags	array	All tags associated with this manifest
updated_at	string (date-time)	The time the manifest was last updated. (example: 2020-04-09T23:54:25Z)

Methods

The following methods are available for this resource:

Name	Accessible by	Required Params	Optional Params	Description
registries_list_repository_manifests	select	registry_name, repository_name	per_page, page	To list all manifests in your container registry repository, send a GET request to /v2/registries/$REGISTRY_NAME/repositories/$REPOSITORY_NAME/digests. Note that if your repository name contains / characters, it must be URL-encoded in the request URL. For example, to list manifests for registry.digitalocean.com/example/my/repo, the path would be /v2/registry/example/repositories/my%2Frepo/digests. It is similar to /v2/registry/$REGISTRY_NAME/repositories/$REPOSITORY_NAME/digests and exists for backward compatibility.
registries_delete_repository_manifest	delete	registry_name, repository_name, manifest_digest		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 be URL-encoded in the request URL. For example, to delete registry.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.
registry_list_repository_manifests_legacy	exec	registry_name, repository_name	per_page, page	To list all manifests in your container registry repository, send a GET request to /v2/registry/$REGISTRY_NAME/repositories/$REPOSITORY_NAME/digests. Note that if your repository name contains / characters, it must be URL-encoded in the request URL. For example, to list manifests for registry.digitalocean.com/example/my/repo, the path would be /v2/registry/example/repositories/my%2Frepo/digests.
registry_delete_repository_manifest_legacy	exec	registry_name, repository_name, manifest_digest		To delete a container repository manifest by digest, send a DELETE request to /v2/registry/$REGISTRY_NAME/repositories/$REPOSITORY_NAME/digests/$MANIFEST_DIGEST. Note that if your repository name contains / characters, it must be URL-encoded in the request URL. For example, to delete registry.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.

Parameters

Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.

Name	Datatype	Description
manifest_digest	string	The manifest digest of a container registry repository tag. (example: sha256:cb8a924afdf0229ef7515d9e5b3024e23b3eb03ddbba287f4a19c6ac90b8d221)
registry_name	string	The name of a container registry. (example: example)
repository_name	string	The name of a container registry repository. If the name contains / characters, they must be URL-encoded, e.g. %2F. (example: repo-1)
page	integer	Which 'page' of paginated results to return. (example: 1)
per_page	integer	Number of items returned per page (example: 2)

SELECT examples

registries_list_repository_manifests

To list all manifests in your container registry repository, send a GET
request to /v2/registries/$REGISTRY_NAME/repositories/$REPOSITORY_NAME/digests.

Note that if your repository name contains / characters, it must be
URL-encoded in the request URL. For example, to list manifests for
registry.digitalocean.com/example/my/repo, the path would be
/v2/registry/example/repositories/my%2Frepo/digests.

It is similar to /v2/registry/$REGISTRY_NAME/repositories/$REPOSITORY_NAME/digests and exists for backward compatibility.

SELECT
registry_name,
blobs,
compressed_size_bytes,
digest,
repository,
size_bytes,
tags,
updated_at
FROM digitalocean.container_registry.repository_manifests
WHERE registry_name = '{{ registry_name }}' -- required
AND repository_name = '{{ repository_name }}' -- required
AND per_page = '{{ per_page }}'
AND page = '{{ page }}';

DELETE examples

registries_delete_repository_manifest

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 be
URL-encoded in the request URL. For example, to delete
registry.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.

DELETE FROM digitalocean.container_registry.repository_manifests
WHERE registry_name = '{{ registry_name }}' --required
AND repository_name = '{{ repository_name }}' --required
AND manifest_digest = '{{ manifest_digest }}' --required;

Lifecycle Methods

registry_list_repository_manifests_legacy

To list all manifests in your container registry repository, send a GET
request to /v2/registry/$REGISTRY_NAME/repositories/$REPOSITORY_NAME/digests.

Note that if your repository name contains / characters, it must be
URL-encoded in the request URL. For example, to list manifests for
registry.digitalocean.com/example/my/repo, the path would be
/v2/registry/example/repositories/my%2Frepo/digests.

EXEC digitalocean.container_registry.repository_manifests.registry_list_repository_manifests_legacy 
@registry_name='{{ registry_name }}' --required, 
@repository_name='{{ repository_name }}' --required, 
@per_page='{{ per_page }}', 
@page='{{ page }}';

registry_delete_repository_manifest_legacy

To delete a container repository manifest by digest, send a DELETE request to
/v2/registry/$REGISTRY_NAME/repositories/$REPOSITORY_NAME/digests/$MANIFEST_DIGEST.

Note that if your repository name contains / characters, it must be
URL-encoded in the request URL. For example, to delete
registry.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.

EXEC digitalocean.container_registry.repository_manifests.registry_delete_repository_manifest_legacy 
@registry_name='{{ registry_name }}' --required, 
@repository_name='{{ repository_name }}' --required, 
@manifest_digest='{{ manifest_digest }}' --required;