kilolock.dev

Status, History, and Repair

Kilolock is useful not only when applying changes, but also when you need to inspect or repair state more surgically.

Check state status

kl status example

This gives you a compact operational view of:

• lineage
• current serial
• lock mode
• coexistence mode
• Terraform version
• resource count
• active lock / in-flight apply context when relevant

Inspect state version history

kl history example

This is a much clearer workflow than manually moving through raw state versions.

Roll back a specific resource

kl rollback resource --address time_sleep.slow_a --to @1

This highlights a key difference from vanilla Terraform backend workflows: Kilolock is trying to expose resource-level operational tooling, not just blob storage.

Abort a stuck apply

kl apply abort --state example --latest

For teams dealing with shared state and long-running workflows, this is a concrete operational capability, not just a theoretical one.

Related docs

• Apply Abort Runbook
• Resource-Level Emergency Repair