Draft spec for #341, for review before anything is built: docs/spec/features/blob-store-copy-ahead.md.
An administrator plans a blob store change by giving the new store's settings. The server copies everything into it while the current store is still the blob store. When the setting switches, the planned change becomes the change, and its copy is a last pass for what was written in between.
Four open questions at the end, each with a recommendation:
Deletes on the current store also go to the planned target, so it doesn't keep orphans. Recommended: yes.
New writes also go to the target. Recommended: no, it would put the target on the mail path.
An apply action writes the target's settings to x:BlobStore, so nobody retypes credentials. Recommended: yes.
Planning is refused while another change is unresolved. Recommended: refuse.
Draft spec for #341, for review before anything is built: `docs/spec/features/blob-store-copy-ahead.md`.
An administrator plans a blob store change by giving the new store's settings. The server copies everything into it while the current store is still the blob store. When the setting switches, the planned change becomes the change, and its copy is a last pass for what was written in between.
Four open questions at the end, each with a recommendation:
1. Deletes on the current store also go to the planned target, so it doesn't keep orphans. Recommended: yes.
2. New writes also go to the target. Recommended: no, it would put the target on the mail path.
3. An `apply` action writes the target's settings to `x:BlobStore`, so nobody retypes credentials. Recommended: yes.
4. Planning is refused while another change is unresolved. Recommended: refuse.
Spec only; no code. Refs #341.
jcoffey-dev
changed title from Spec: copying blobs ahead of a blob store change (draft) to Spec: copying blobs ahead of a blob store change2026-11-10 06:20:49 +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.
Draft spec for #341, for review before anything is built:
docs/spec/features/blob-store-copy-ahead.md.An administrator plans a blob store change by giving the new store's settings. The server copies everything into it while the current store is still the blob store. When the setting switches, the planned change becomes the change, and its copy is a last pass for what was written in between.
Four open questions at the end, each with a recommendation:
applyaction writes the target's settings tox:BlobStore, so nobody retypes credentials. Recommended: yes.Spec only; no code. Refs #341.
Spec: copying blobs ahead of a blob store change (draft)to Spec: copying blobs ahead of a blob store change