stackkit drift detect, stackkit drift reconcile
stackkit drift detect
Read the authoritative local state and report drift. Read and verify the canonical ResolvedPlan, generated artifacts, owner-signed Apply evidence, local Owner binding, and live Basement Compose runtime without refreshing runtime state. Under the terramate generation target it also runs a read-only detailed-exitcode OpenTofu plan through Terramate in every stack of the local host project and adds one stacks entry per stack; it never applies. The content-addressed report is retained as local Owner evidence for every selected Application Kit.
Examples
stackkit drift reconcile
Reconcile drift through the governed local lifecycle. Standard mode requires explicit local Owner approval, verifies the current local authority, creates a mandatory Kopia and executor-state rollback checkpoint, then runs generate, apply, and verify through the exclusive lifecycle journal. A failed target phase automatically restores, reapplies, and verifies the captured prior executor state. Advanced mode remains fail-closed until an offline-verified capability is supplied. It runs through an exact Owner-signed change set, which is empty for runtime drift: it observes the per-stack drift, forces every drifted Terramate stack to re-converge by replacing its wrapper up trigger, applies through the governed transaction, then observes the drift report again, including every Terramate stack plan, and fails unless the post-reconcile report is clean.
Examples