{"command":{"effect":"write","timeoutSeconds":30,"inputSchema":{"type":"object","description":"Garbage collection enables users to clear out unreferenced blobs (layer &\nmanifest data) after deleting one or more manifests from a repository. If\nthere are no unreferenced blobs resulting from the deletion of one or more\nmanifests, garbage collection is effectively a noop.\n[See here for more information](https://docs.digitalocean.com/products/container-registry/how-to/clean-up-container-registry/)\nabout how and why you should clean up your container registry periodically.\n\nTo request a garbage collection run on your registry, send a POST request to\n`/v2/registries/$REGISTRY_NAME/garbage-collection`. This will initiate the\nfollowing sequence of events on your registry.\n\n* Set the registry to read-only mode, meaning no further write-scoped\n  JWTs will be issued to registry clients. Existing write-scoped JWTs will\n  continue to work until they expire which can take up to 15 minutes.\n* Wait until all existing write-scoped JWTs have expired.\n* Scan all registry manifests to determine which blobs are unreferenced.\n* Delete all unreferenced blobs from the registry.\n* Record the number of blobs deleted and bytes freed, mark the garbage\n  collection status as `success`.\n* Remove the read-only mode restriction from the registry, meaning write-scoped\n  JWTs will once again be issued to registry clients.\n","properties":{"path":{"type":"object","properties":{"registry_name":{"type":"string","examples":["example"],"description":"The name of a container registry."}},"required":["registry_name"],"additionalProperties":false}},"required":["path"],"additionalProperties":false},"name":"Start Garbage Collection","id":"digitalocean.registries_run_garbagecollection","example":{"path":{"registry_name":"example"}},"maxRequests":1,"summary":false}}