Spaces epic batch 4: rename a space — flip, alias, converge (+ handbook page) #771

Closed
opened 2026-09-26 16:02:32 +00:00 by Cordy · 0 comments
Owner

Final batch of the Spaces epic (rev3 panel 6 + ADR 0002; depends on #768; its own release — the riskiest surface gets the quietest week).

Flip: POST /api/v1/spaces/{name}/rename (owner + admin, app-owned only) = one registry write: name flips, backendDir stays. Old name becomes an alias immediately; both resolve to the same ID + backend dir. Zero rewrites: old share links, holds, locks, mid-flight tus uploads, WebDAV mounts and peering keep working.

Alias lifecycle: aliases point at IDs (no chains by construction); old name reserved (Create refuses while alias lives, tombstone logic); admin inventory lists aliases with an explicit, audited retire action; web UI hints on entry through a former name. Audit verbs: space-rename, space-alias-retired (registry entries in verbs.go).

Converge: background job renames the backend dir then flips backendDir in one write. POSIX immediate; S3/encrypted restartable when idle. Correctness never depends on it; registry is authoritative for restores during divergence.

Resolver wiring: this is the batch where scope//dav resolution goes through the registry (name-or-alias → id → backendDir) — the hot-path change, measured in the gate.

IdP relink: the #715 orphan surface gains "Relink" — renamed IdP group re-attached, old group name aliased, ID keeps cosmetics/holds/sizes. Detection stays manual under OIDC (#129 constraint); LDAP entryUUID auto-follow noted as future.

Docs (release gate): docs/handbook/spaces-rename.md per rev3 panel 7 — allowed, safe, not recommended as routine; what keeps working; the pitfalls we handle and the ones we cannot; operator notes (audit events, converge status, mid-converge backups).

Batch gate: rename invariants end-to-end (flip visible both names, alias permanence, reservation, converge idempotence/restart, retire semantics) + both suites.

Final batch of the Spaces epic (rev3 panel 6 + ADR 0002; depends on #768; its own release — the riskiest surface gets the quietest week). **Flip:** `POST /api/v1/spaces/{name}/rename` (owner + admin, app-owned only) = one registry write: `name` flips, `backendDir` stays. Old name becomes an alias immediately; both resolve to the same ID + backend dir. Zero rewrites: old share links, holds, locks, mid-flight tus uploads, WebDAV mounts and peering keep working. **Alias lifecycle:** aliases point at IDs (no chains by construction); old name reserved (`Create` refuses while alias lives, tombstone logic); admin inventory lists aliases with an explicit, audited retire action; web UI hints on entry through a former name. Audit verbs: `space-rename`, `space-alias-retired` (registry entries in verbs.go). **Converge:** background job renames the backend dir then flips `backendDir` in one write. POSIX immediate; S3/encrypted restartable when idle. Correctness never depends on it; registry is authoritative for restores during divergence. **Resolver wiring:** this is the batch where scope//dav resolution goes through the registry (name-or-alias → id → backendDir) — the hot-path change, measured in the gate. **IdP relink:** the #715 orphan surface gains "Relink" — renamed IdP group re-attached, old group name aliased, ID keeps cosmetics/holds/sizes. Detection stays manual under OIDC (#129 constraint); LDAP entryUUID auto-follow noted as future. **Docs (release gate):** `docs/handbook/spaces-rename.md` per rev3 panel 7 — allowed, safe, not recommended as routine; what keeps working; the pitfalls we handle and the ones we cannot; operator notes (audit events, converge status, mid-converge backups). Batch gate: rename invariants end-to-end (flip visible both names, alias permanence, reservation, converge idempotence/restart, retire semantics) + both suites.
Cordy referenced this issue from a commit 2026-09-26 19:06:52 +00:00
Cordy closed this issue 2026-09-26 19:11:54 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#771
No description provided.