Detach a volume from an instance
On a stopped instance it's synchronous and the volume becomes available. The root volume can't be detached (409 root_volume). On a running instance it's asynchronous: 202 with a DetachVolume operation, which waits for the guest to release the disk; force frees the volume without the guest (the guest sees I/O errors on it and may lose writes it hadn't made). A repeat answers the open operation, and a repeat with force escalates it. 409 volume_detaching while a force-detached disk is still in the guest.
https://compute-api.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/instances/{instance}/detach-volumeAuthorization
Path parameters
Header parameters
Request bodyJSONrequired
Returns
200
The instance, with the change.
202
The operation, which Location names; poll it until it finishes.
400
invalid_request (with issues), invalid_cursor, or the endpoint's own 400 codes.
403
access_denied: the caller's policies don't allow the action; forbidden_origin: a cookie-authenticated write from an origin that isn't allowed; spend_limit_reached.
404
not_found: unknown, malformed, or in an organization the caller isn't in.
409
quota_exceeded (an allocation quota, with quota), idempotency_conflict, idempotency_in_progress (with Retry-After), organization_deletion_pending, operation_in_progress, or the endpoint's own 409 codes.
413
payload_too_large: the body is over the endpoint's limit (1 MiB unless it says otherwise).
429
too_many_requests, with Retry-After; or quota_exceeded (a rate, usage or concurrency quota, with quota), never with Retry-After.
500
internal_error: a bug; the details are in the logs, under the request ID.