Delete a protection group
DELETE/v1/protection-groups/:id
Stops protecting the servers as a group. The servers themselves are not touched. Only a group with no disaster recovery run acting on it can be deleted. The group's runs and their journals go with it; the record of what those runs created stays until each item marked for teardown has been removed. Deleting a recovery, which only an operator may do, also deletes the recovery bindings it created; bindings it found already in place stay, and so do the backups already adopted and any standby.
A recovery whose runs built servers, volumes, ports or floating addresses here and kept them is not deleted while they are still held, because nothing here could see or remove them afterwards: retire it first, which removes what a superseded recover built, or, where the workload runs here, fail it back first. With keep_resources=true it is deleted anyway and every one of them is left where it is, as the project's own; the deletion's audit record names them.
Any member of the project the token is scoped to.
Request
Responses
- 204
- 400
- 401
- 403
- 404
- 409
- default
No Content
Bad Request.
invalid_request: A query parameter is malformed.
Unauthorized.
unauthenticated: The token is missing, expired or not valid.
Forbidden.
forbidden: The token may not change groups in the group's project, or the group is a recovery and the token is not a system-scoped admin token.
Not Found.
not_found: No group with this id exists in the token's project.
Conflict.
group_busy: A run is acting on the group, so active_run_id is set or its state is that of a running operation.
group_holds_resources: The group is a recovery, and servers, volumes, ports or floating addresses its runs built and kept are still held, and keep_resources is not true. fields names each as resources.<id>, and detail says whether to retire or fail back first.
An error, as an RFC 7807 problem document.