deckctl history
Handles history lifecycle. Every successful template apply appends a record to
a bbolt database, by default at
~/.config/deckctl/history.db. Dry runs are not recorded.
Synopsis
Section titled “Synopsis”deckctl history [command] [flags]| Subcommand | Purpose |
|---|---|
list | List all recorded applies |
clear | Delete all records |
All subcommands also accept the global flags,
notably --history.
deckctl history list
Section titled “deckctl history list”deckctl history list [flags]No command-specific flags. Table columns: Timestamp, Template, Source,
Output.
deckctl history listdeckctl history list -o jsondeckctl history list --history /tmp/deckctl-history.dbRecord shape
Section titled “Record shape”-o json returns the full record, including the resolved variables that the
table view omits:
[ { "timestamp": "2026-06-17T21:04:11.482913Z", "template": "go-service", "source": "work", "output_path": "./billing", "variables": { "app_name": "billing", "replicas": "3" } }]Records are keyed by timestamp (RFC 3339 with nanoseconds, UTC), so they come back in chronological order.
# The last five appliesdeckctl history list -o json | jq -r '.[-5:] | .[] | "\(.timestamp) \(.template) → \(.output_path)"'
# Re-run a previous apply's variablesdeckctl history list -o json \ | jq -r '.[-1].variables | to_entries[] | "--var \(.key)=\(.value)"'deckctl history clear
Section titled “deckctl history clear”deckctl history clear [flags]| Flag | Default | Description |
|---|---|---|
--auto-approve | false | Skip the confirmation prompt |
Removes all records — there is no per-entry or date-range filter.
deckctl history cleardeckctl history clear --auto-approve