Blob store changes: plan one ahead, copy ahead, apply #355

Merged
jcoffey-dev merged 1 commits from feat/341-copy-ahead into main 2026-11-10 06:57:39 +00:00
1 Commits
Author SHA1 Message Date
jcoffey-dev 64d7f484c4 Blob store changes: plan one ahead, copy ahead, apply
ci / fork-checks (pull_request) Skipped
ci / build (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 10m7s
A create of inbuxa:BlobStoreChange with a target (an x:BlobStore value)
plans a change from where the blob store is now. The target is opened
and probed first; planning is refused for the same place, a second
plan, an unsettled change, or a store that can't be written.

Copying a planned change copies from the current store to the planned
one, with the same walk, checks and throttle as the copy after a
change. While it's planned, deletes on the current store also go to
the planned store. Nothing reads from it and a snapshot isn't refused.

apply writes the target to the blob store setting once the copy ahead
ended copied. When a node starts with that setting, the planned change
becomes the change, with the copy ahead kept as copiedAhead, so the
last pass copies only what was written in between.

The server now keeps its blob store in the read-through wrapper from
start-up, so a plan takes effect without a restart. A planned store's
settings are never returned and are redacted in the audit log.

Spec: docs/spec/features/blob-store-copy-ahead.md (#341).
2026-11-09 23:43:09 -07:00