Out Plane
volume

volume detach

Unmount a disk, keeping it and its contents.

writesrepeatable--dry-run

Unmounts a disk, keeping it and everything on it. The application loses the mount at its next deployment.

This is what has to happen before a disk can be deleted.

Usage

outplane volume detach <VOLUME> [flags]

Arguments

ArgumentTypeDescription
VOLUMEstringVolume name or id. Required.

Flags

FlagTypeDescription
--deployboolDeploy afterwards, so the mount reaches the running app.

The global flags apply as well.

Output

FieldTypeDescription
idstring
namestring
sizeGbint10 to 50, and fixed once created.
statusstringOne of attached, detached.
appstring | nullThe application it is mounted on.
appIdstring | null
mountPathstring | nullWhere it appears inside the container.
accessModestringAlways ReadWriteOnce: one instance mounts it at a time.
createdAtstring | nullRFC 3339, UTC.
changedbool

Examples

Unmount a disk

outplane volume detach data

See which application would lose it

outplane volume detach data --dry-run --json
{
  "app": "checkout",
  "changed": false,
  "name": "data"
}

Detach it and deploy, so the running app loses the mount now

outplane volume detach data --deploy --json --fields app,changed

What to Know

  • Detaching is not deleting. The disk keeps its contents and its cost, and can be mounted again.
  • A disk that is not attached reports changed false and exits 0.
  • The application loses the mount at its next deployment.

Errors

Beyond 0 for success, this command exits with:

ExitKindMeaning
2usageInvalid arguments, unknown flag, or client-side validation failure.
3authNot authenticated, token revoked or expired, or forbidden for this team.
5not_foundThe named resource does not exist, or is not visible to this credential.
8upstreamThe Out Plane API returned a server error.

The code on the error object is one of volume.not_found, usage.missing_argument. Branch on that, or on the exit status. The message is prose and changes.

On this page