Skip to content

Attest the state file a failed apply rewrote #36

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gsavage merged 2 commits into from
Oct 7, 2026
Merged

Attest the state file a failed apply rewrote #36

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1359dc2
Attest the state file a failed apply rewrote
JonJagger Oct 7, 2026
36b1732
Keep a failed apply non-compliant, and document why
JonJagger Oct 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -259,6 +259,13 @@ Both workflows can optionally attest each Terraform run to Kosli. This is opt-i
that any later out-of-band change to either file is detected as drift by the downstream
[drift-detection job][drift-doc].

A failed `tf apply` attests nothing, deliberately. Terraform writes the state file as it goes, so
an apply that fails part-way can leave a rewritten state file that has no provenance in Kosli, and
the [drift-detection job][drift-doc] reports it as drift. That is the intended outcome: the
infrastructure is only partly at the merged commit, so it should not be reported as compliant.
The environment stays non-compliant until an apply of the same component succeeds, so once the
cause of the failure is fixed, re-run the apply.

The trail template needs to declare every attestation/artifact name the workflow emits:

```yaml
Expand Down
Loading