playhouse delete

Delete a Playhouse and the Kubernetes cluster behind it. Guarded against deleting a Playhouse that still contains Playrooms.

Alpha

This command is in active development. Flags and behaviour may change between releases.

Delete a Playhouse: the Kubernetes cluster that hosts Playrooms.

Destructive action

This deletes the whole cluster. Any Playrooms still inside it, and all their data, are destroyed. This cannot be undone.

Before deleting, the Playhouse is checked for Playrooms: deletion is refused while any exist (running or stopped). Pass --force to skip that check. You also need --force when the Playhouse is stopped or unreachable, since the check requires connecting to it. You are asked to confirm unless --yes is given; --force does not skip the confirmation.

By default delete waits until the cluster is fully gone before returning. Pass --no-wait to return as soon as the deletion is issued.

acloud playhouse delete NAME [flags]

The name must be typed out in full. The - (last-used) shortcut and cached defaults that Playroom commands accept are not supported for delete. Aliased as rm.

Examples

acloud playhouse delete playhouse-demo

acloud playhouse delete playhouse-demo --yes

# delete even though Playrooms may still be inside (destroys them and their data)
acloud playhouse delete playhouse-demo --force

Expected output

By default it waits for the cluster to disappear:

Delete playhouse my-org/sandbox/playhouse-demo? This deletes the cluster [y/N]: y

Waiting for playhouse playhouse-demo to be deleted... done
Deleted playhouse my-org/sandbox/playhouse-demo

With --no-wait, it returns as soon as the deletion is issued:

Deleting playhouse my-org/sandbox/playhouse-demo (--no-wait; not waiting for the cluster to be gone).

With --force, the prompt instead warns that the Playroom check is being skipped and that any Playrooms and their data will be destroyed.

Common errors

Not a Playhouse: cluster "…" is not a Playhouse (expected name prefix "playhouse-").
Wrong status: can only delete playhouses with status 'running' or 'stopped'.
Playrooms still inside: playhouse "…" still contains N playroom(s). Delete them first (acloud playroom delete NAME -p SLUG) or pass --force.
Can't verify it's empty: cannot verify playhouse "…" is empty. The check couldn't connect; pass --force to delete anyway.
Name not typed in full: passing - or relying on a cached default is rejected for delete.

Options

Prop

Type

Options inherited from parent commands