Adds docs/spec/features/blob-store-cleanup.md for #342, with links from SPEC.md and the blob store change spec.
A resolved change keeps its old store's settings, and action: "cleanUp" deletes from the old store each blob it has checked in the new one (read back and hash-checked). Blobs that fail the check stay in the old store and are reported. There's a preview (dryRun) first. A real run needs confirm set to the change's id, because backups of the data store taken before the change still need the old store's blobs. It's refused while any node still runs on the old store, while the two stores overlap, or after a change back to the old store. Each node now records where its blob store is with the minute poll it already does.
Four open questions at the end, each with a recommendation. Docs only.
Adds `docs/spec/features/blob-store-cleanup.md` for #342, with links from SPEC.md and the blob store change spec.
A resolved change keeps its old store's settings, and `action: "cleanUp"` deletes from the old store each blob it has checked in the new one (read back and hash-checked). Blobs that fail the check stay in the old store and are reported. There's a preview (`dryRun`) first. A real run needs `confirm` set to the change's id, because backups of the data store taken before the change still need the old store's blobs. It's refused while any node still runs on the old store, while the two stores overlap, or after a change back to the old store. Each node now records where its blob store is with the minute poll it already does.
Four open questions at the end, each with a recommendation. Docs only.
jcoffey-dev
changed title from Spec: cleaning up the old store after a blob store change (draft) to Spec: cleaning up the old store after a blob store change2026-11-10 17:04:24 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds
docs/spec/features/blob-store-cleanup.mdfor #342, with links from SPEC.md and the blob store change spec.A resolved change keeps its old store's settings, and
action: "cleanUp"deletes from the old store each blob it has checked in the new one (read back and hash-checked). Blobs that fail the check stay in the old store and are reported. There's a preview (dryRun) first. A real run needsconfirmset to the change's id, because backups of the data store taken before the change still need the old store's blobs. It's refused while any node still runs on the old store, while the two stores overlap, or after a change back to the old store. Each node now records where its blob store is with the minute poll it already does.Four open questions at the end, each with a recommendation. Docs only.
Spec: cleaning up the old store after a blob store change (draft)to Spec: cleaning up the old store after a blob store change