Skip to content
docs.deliberate

CLI

The CLI separates desired-state reconciliation from necessary runtime actions.

Desired state

Section titled “Desired state”
Terminal window
deliberate apply --env production
deliberate apply --env preview-pr-42 --image app=registry.deliberate.cloud/acme/app:git-a81c9e4
deliberate diff --env production
deliberate pull --env production
deliberate clone <team-slug>/production

apply validates and reconciles the complete .deliberate/ tree. pull replaces the local resource tree with the selected remote revision. Commit or stash local work before pulling. Repeat --image <component>=<reference> to deploy immutable images from CI without editing the checkout. The CLI resolves those assignments into the tree before diffing and validation; the stored revision and a later pull contain the exact deployed references.

Inspect

Section titled “Inspect”
Terminal window
deliberate status
deliberate open --env production
deliberate logs --env production --component app
deliberate metrics --env production --component app
deliberate deployments list --env production

Runtime operations

Section titled “Runtime operations”

Runtime operations remain procedural because they represent actions rather than desired state:

Terminal window
deliberate exec --env production --component app -- sh
deliberate databases backup postgres --env production
deliberate deployments rollback --env production <revision>

Use deliberate <command> --help for the authoritative flags and subcommands of the installed release.