← Back to list
01Issue
FeatureOpenSwamp CLIPublic
AssigneesNone
Relationships
#4678 swamp behavior type rename: move a behavior type's data, outputs and catalog rows to a new type name
Opened by zack · 11/12/2026
Follow-up to #4502, split out from it. #4502 ships swamp data reindex (rebuild the catalog from disk and drop rows with no file behind them) and a docs note on renaming a type by hand. This issue covers the dedicated command.
Proposed
swamp behavior type rename : moves the data, outputs and definitions-evaluated folders from the old type to the new one and rewrites the catalog rows, holding the repo's locks. It refuses while serve or a run is active and prints what changed.
Design questions
- Resumability: a rename interrupted halfway must be safe to re-run and finish.
- Remote datastores (S3, datastore v3 commit log) cannot move a folder; decide whether rename is a copy plus delete, a log-level rename record, or refused on those datastores.
- Workflow run records keep modelType per step. Rewriting them keeps history links working; leaving them makes history show the old name.
- Extension source and definition YAML still carry the old type string; decide whether the command rewrites them or only the stored data.
Originally requested by liywjl in #4502 (co-author credit requested).
02Bog Flow
Open
No activity in this phase yet.
03Sludge Pulse
Sign in to post a ripple.