Delete snapshot of a virtual server
Delete one snapshot of a vServer - the server itself is not touched.
manitu_vserver_snapshot_delete on https://mcp.manitu.de/mcpAnnotations as tools/list sends them
Description for the model
Deletes one snapshot of a virtual server (vServer), by its vserver_id and the snapshot_id from manitu_vserver_snapshot_list. The server keeps running as it is; only the state the snapshot holds is gone for good. Ask the customer for an explicit yes first, naming the snapshot by its date and note. Runs in the background: the answer is the workflow started (see pending_workflow_list of manitu_vserver_get for its progress). Refused with a conflict while another workflow runs on the vServer (blocked_by names it - wait for it, do not retry at once) or while it cannot be changed.
Arguments
vserver_idinteger | stringrequiredThe vserver_id from manitu_vserver_list - never guess one.
snapshot_idstringrequiredThe snapshot_id from manitu_vserver_snapshot_list - never guess one.
Result structuredContent, checked against the schema
workflowstringrequiredWhat is being done, e.g. a reboot.
workflow_idstringrequiredThe id of this run of the workflow.
created_atstring | nullrequiredWhen it was asked for.
started_atstring | nullrequiredWhen it started; null while it waits for the next run - usually a minute or two, at times longer. Nothing to tell the customer unless asked.
workflow_tokenstring | nullrequiredPass it to manitu_workflow_get to see how far the workflow is - as it is, never built or changed. A secret of this workflow: do not show it to anyone. null if there is none.
taskobjectrequiredThe task the customer panel polls for its progress.
task.idintegerrequiredtask.authstringrequiredAuthentication
One of X-API-Key, Authorization: Bearer … - never more than one in a request. More
Request body JSON; unknown fields are refused
vserver_idinteger | stringrequiredThe vserver_id from manitu_vserver_list - never guess one.
snapshot_idstringrequiredThe snapshot_id from manitu_vserver_snapshot_list - never guess one.
Response in data; the rest of the body as on every call
workflowstringrequiredWhat is being done, e.g. a reboot.
workflow_idstringrequiredThe id of this run of the workflow.
created_atstring | nullrequiredWhen it was asked for.
started_atstring | nullrequiredWhen it started; null while it waits for the next run - usually a minute or two, at times longer. Nothing to tell the customer unless asked.
workflow_tokenstring | nullrequiredPass it to manitu_workflow_get to see how far the workflow is - as it is, never built or changed. A secret of this workflow: do not show it to anyone. null if there is none.
taskobjectrequiredThe task the customer panel polls for its progress.
task.idintegerrequiredtask.authstringrequiredStatuses
200Success.400The request does not match the declared input schema.401No credential was presented, or it was not recognised.403The credential is not permitted to use this operation.500The server failed. Nothing about the request was wrong. Whether a change took effect is not known - check before trying it again.503The channel this operation forwards through is unavailable.