Developer Documentation
Delete Registries Harbor Projects
Released in v7.0.0Deletes the specified project from Harbor registry. Repositories and images in the project will be removed upon project deletion. Storage space of deleted images in the project will be reclaimed through next scheduled Harbor registry garbage collection. In vSphere 7.0, a Harbor registry is deployed in a vSphere cluster with vSphere namespaces enabled. When a namespace is deleted, a project with same name as the namespace is deleted from the Harbor registry, so this operation should not be called.
Request
URLURL
https://{api_host}/rest/vcenter/content/registries/harbor/{registry}/projects/{project}
Path Parameters
Path Parameters
| Required | Parameter Name | Type | Description |
|---|---|---|---|
| required |
|
string | Identifier of the registry. The parameter must be an identifier for the resource type: com.vmware.vcenter.content.Registry. |
| required |
|
string | Identifier of the Harbor project. The parameter must be an identifier for the resource type: com.vmware.vcenter.content.Registry.Harbor.Project. |
Errors
| Code | Returns | Description |
|---|---|---|
| 401 | Error | com.vmware.vapi.std.errors.unauthenticated : if the user can not be authenticated. | com.vmware.vapi.std.errors.unauthorized : if the user does not have ContentLibrary.ManageRegistryProject privilege. |
| 404 | Error | com.vmware.vapi.std.errors.not_found : if registry or project cannot be found. In vSphere 7.0, the existing project could have been deleted automatically when a namespace with the same name is deleted. | com.vmware.vapi.std.errors.error : if the system reports an error while responding to the request. |
| 409 | Error | com.vmware.vapi.std.errors.not_allowed_in_current_state : if Harbor registry is being deleted. |
| default | Error | Not available |
