​

Usage

helix delete <INSTANCE> [OPTIONS]

​

Arguments

​

Options

​

Behavior

• For local instances, Helix-owned containers, networks, disk-mode and disk-cache volumes, and the per-instance directory under .helix/ are deleted.
• For Helix Cloud instances, only the [enterprise.<name>] block in helix.toml is removed — the database itself is untouched.
• Remote S3 object-store data is not deleted.
• The CLI refuses to delete the last instance in helix.toml; add a replacement first.
• In a TTY, helix delete prints a warning and asks for confirmation. Without a TTY, or with --json, it refuses to run without --yes:
  refusing to delete '<instance>' without confirmation
  

​

Examples

# Delete a local instance (TTY)
helix delete staging

# Delete non-interactively
helix delete staging --yes

​

Related

• helix prune — clean up local state but keep the instance in helix.toml.
• helix add — add a replacement instance.
• CLI configuration — the helix.toml format.