Volumes
Detach a volume
Detach a volume from its application at the next deploy, keeping its data.
Updated
https://cloud.cahaves.com/api/volumes/{id}
Authorization
cahaves.cloud.sessionstringcookierequired
The session cookie Cloud sets when a customer signs in to the console with GitHub or Google. It is HttpOnly, so scripts cannot read it, and there are no API keys or tokens yet.
Path parameters
idstring<uuid>required
Example: "4b6d8f0a-1c3e-4a5b-8d7f-9e0a1b2c3d4e"
Headers
X-Cloud-Organizationstring<uuid>
The id of the organization the request works in, one the signed-in customer owns. Left out or empty, the request works in their oldest organization. Any other value answers 404 with `reason: "organization"`. A customer with no organization yet gets 409 "Create an organization first." from every route that works in one.
Example: "2f6c8e0a-4b1d-4e7f-9a3c-5d7e9f1b3a5c"
Responses
Detached.
This response has no body.
The container keeps the mount until the application's next deploy, and the stored data is not erased. Cloud archives the automatic schedule it created for the volume.
| Status | Sentence |
|---|---|
409 | Backup history still references this volume. |
409 | Reconcile this volume attachment before removing it. |
409 | Wait for the service deployment to finish. |
409 | This service has unfinished backup work. |
The first means a schedule you created still backs the volume up; remove it first. The second means the attachment is unconfirmed; send Attach a volume again with the same service and path to confirm it.