Undelete building block
POST/api/meshobjects/meshbuildingblocks/:uuid/undelete
Takes back the deletion of a meshBuildingBlock. A meshBuildingBlock whose destroy run keeps failing stays marked for deletion, and every further run tries to destroy it again. After the undelete, it is no longer marked for deletion and runs like any other meshBuildingBlock: when it needs a run, meshStack starts one, and approval policies apply as usual. This request does not force a run.
The request is rejected with 400 Bad Request when the meshBuildingBlock is not marked for deletion. It is
rejected with 409 Conflict while the deletion run is pending or in progress, when the meshBuildingBlock is being
purged or is already deleted, while a meshBuildingBlock that depends on it is marked for deletion, while its
building block definition is being deleted, and while its tenant is being deleted.
Admins and the workspace that owns the building block definition may undelete. They need both the right to save and the right to delete building blocks.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 406
- 409
The meshBuildingBlock is no longer marked for deletion
The request is invalid. The message names the invalid part.
The request has no valid authentication.
The authenticated user or API key lacks the permission for this request.
The resource does not exist, or you may not see it.
The Accept header names no media type of this operation, or a version that is no longer supported.
The request conflicts with the current state, for example with an existing object of the same name. The message names the conflict.