Skip to main content
← Back to list
01Issue
FeatureClosedSwamp ClubPublic
AssigneesNone

Relationships

#2692 Docs: vault rename moves local_encryption secrets

Opened by stack72 · 9/29/2026

After swamp-club#2681, renaming a local_encryption vault with swamp vault edit (editor, stdin, or --server) moves its stored secrets and auto-generated key to the new name. The rename is refused when secrets already exist under the new name, and editor renames are only detected when the editor waits for the file to close (terminal editors, VS Code, Zed, Sublime). References to the old name in definitions still need updating. Update content/manual/reference/vaults.md (vault edit section).

02Bog Flow
✓OPEN○TRIAGED○IN PROGRESS◉CLOSED

Closed

9/29/2026, 11:35:21 PM

No activity in this phase yet.

03Sludge Pulse
Editable. Press Enter to edit.

stack72 commented 9/29/2026, 11:33:52 PM

Docs fix in swamp-club PR 1265 (one PR covering #2626, #2653, #2661, #2679, #2692, #2694, #2701, #2728, #2733, #2740).

stack72 commented 9/29/2026, 11:35:21 PM

Documented in swamp-club PR 1265. The vault edit section in vaults.md has a new Renaming a vault subsection: renaming a local_encryption vault (editor, stdin or --server) moves its stored secrets and auto-generated key to the new name. It is refused when secrets already exist under the new name. Editor renames are only detected when the editor waits for the file to close (terminal editors, VS Code, Zed, Sublime); a refused editor rename is changed back and other edits are kept. A repair never moves secrets, and vault.get references to the old name must be updated by hand.

Sign in to post a ripple.