Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLIPublic
Assigneeshammz

Relationships

#2845 Warn when datastore setup keeps managedConfig but the new datastore has no config tier

Opened by hammz · 9/30/2026· Shipped 10/1/2026

Follow-up from swamp-club#2837.

Since swamp-club#2837, swamp datastore setup keeps managedConfig: true in .swamp.yaml instead of silently dropping it. When setup switches a managedConfig repo to a different datastore whose config tier is empty (no managed-config-migrated.json sentinel), the repo stays managed against an empty tier and model, workflow and vault definitions appear to vanish. Before the fix the same switch silently turned managedConfig off, which was no better.

Proposal

After setup, when managedConfig is on, check the new datastore's config tier for the migration sentinel and emit a warning event (log and json modes) that names the problem and how to populate the tier. Care is needed under lazy hydration, where the sentinel may be present only as metadata.

02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 10 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

10/1/2026, 5:04:41 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
hammz assigned hammz10/1/2026, 3:43:36 PM

Sign in to post a ripple.