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

Relationships

↔ sibling #4727

#4726 Docs: vault manual says legacy vault type names are automatically mapped, but vault create and migrate refuse them

Opened by zack · 11/13/2026

content/manual/reference/vaults.md (around lines 309-310) says legacy type names (aws, aws-sm, azure, azure-kv, 1password) are automatically mapped to their scoped equivalents. That is true only when an already-stored vault config is loaded (vault_service.ts remaps it with a warning). vault create refuses a legacy name with: The type aws-sm has been renamed to @swamp/aws-sm. Use type @swamp/aws-sm instead (src/libswamp/vaults/create.ts). vault migrate refuses one as well (src/libswamp/vaults/migrate.ts), which the same page already states in its migrate table.

Suggested wording: new vaults must use the scoped type name; vault create and vault migrate reject a legacy name with a message naming the scoped type; an existing vault config that still uses a legacy name keeps working and logs a deprecation warning when it loads. Found while triaging swamp-club#4721.

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

Triaged

11/13/2026, 8:07:36 PM

No activity in this phase yet.

03Sludge Pulse
stack72 linked sibling of #472711/13/2026, 8:06:36 PM
Editable. Press Enter to edit.

system commented 11/13/2026, 6:27:02 PM

Classified automatically when this issue was filed.

  • Type: Bug

If you feel this classification is incorrect, add a ripple to tell us so.

Sign in to post a ripple.