Skip to content

Takeover runbook: operator procedure with its qualified scope (#987) #989

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
rmcdaniel merged 1 commit into from
Nov 3, 2026
Merged

Takeover runbook: operator procedure with its qualified scope (#987) #989

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 9 additions & 5 deletions docs/rust-server-storage-audit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,10 @@
# Rust Server storage and upgrade audit

This is a source-audit checkpoint for [#325](https://github.com/durable-workflow/server/issues/325),
not a qualified migration procedure. Rust takeover and stored-value conversion
remain unimplemented. The PHP ownership fence is implemented in source by
not a migration procedure, and it predates the takeover. Native 3.0.x
implements `upgrade-takeover`; its procedure, qualified scope and remaining
gaps are in the [takeover runbook](rust-server-upgrade-takeover.md). The text
below is the original audit. The PHP ownership fence is implemented in source by
[#331](https://github.com/durable-workflow/server/pull/331); the frozen published
reference still lacks that fence. The reference is published Server `2.5.13`, source
`f061d64277f09b11dd9a0844b958bfab6c8e998e`, with Workflow `2.5.4`, source
Expand Down Expand Up @@ -96,7 +98,9 @@ and takeover flag stays false.
There is no mixed PHP/Rust fleet or PHP rollback after upgrade. Restoring a
pre-upgrade backup is a separate recovery action with its own data boundary.

All gates above remain open. The [takeover design](rust-server-upgrade-takeover.md)
proposes how the takeover command proves the backup, excludes other writers and
resumes after interruption. HTTP export/import remains a supported deployment
These gates were written before the takeover existed. The
[takeover runbook](rust-server-upgrade-takeover.md#status-and-scope) records
which are now qualified and which remain open. Its design section describes
how the takeover command proves the backup, excludes other writers and resumes
after interruption. HTTP export/import remains a supported deployment
transfer surface, but it does not substitute for in-place upgrade qualification.
Loading
Loading