Skip to content

Conversation

@varundeepsaini
Copy link
Contributor

Closes: #4090

Changes

Add write-ahead log (WAL) to record state changes during direct deployment, enabling recovery of partial state if deployment is interrupted.

Why

Today, if deployment is interrupted before Finalize(), no state is saved, and created resources become orphaned. The WAL writes each state change immediately to disk and replays them on restart.

Tests

Unit tests added for WAL save/replay, delete/replay, finalize cleanup, and edge cases.

@varundeepsaini varundeepsaini force-pushed the feature/deploy-append-log branch from b51a199 to 7f67cb2 Compare December 6, 2025 19:08
@github-actions
Copy link

github-actions bot commented Dec 6, 2025

An authorized user can trigger integration tests manually by following the instructions below:

Trigger:
go/deco-tests-run/cli

Inputs:

  • PR number: 4106
  • Commit SHA: 7f67cb2642701fcd964506994e38016ec6f54d8e

Checks will be approved automatically on success.

@varundeepsaini
Copy link
Contributor Author

@denik
Had a question, should the WAL be written to a new file, or should it be on the same file as the state ?
If a new file, then any write/read ops to the WAL that give an error, how should they be handled?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

State file append log, avoid orphaned resources on interrupted deploy

1 participant