Skip to main content
← Back to list
01Issue
BugShippedSwamp CLIPublic
Assigneesstack72

Relationships

↔ sibling #3162

#2844 datastore setup can overwrite an existing remote config tier when it moves an in-repo tier into an extension datastore

Opened by zack · 9/30/2026· Shipped 10/7/2026

Follow-up from swamp-club#2837.

What happens

A managedConfig repo on a filesystem datastore at .swamp keeps its config tier in .swamp/config. Running swamp datastore setup extension (S3/GCS) against a datastore whose remote already holds a config tier (for example, a second repo joining a shared, already-migrated datastore) copies .swamp/config into the cache and pushes it before hydrating. The push is last-writer-wins per file, so files such as config/upstream_extensions.json, config/models and config/workflows overwrite the team copies.

swamp-club#2837 fixed the case where .swamp/config is instance-local (the tier lives elsewhere), but deliberately kept migrating a real in-repo tier.

Expected

Setup detects that the remote already has a config tier (for example, the managed-config-migrated.json sentinel) and either refuses, or hydrates first and skips or merges conflicting config-tier files.

Notes

The sync service has no path filter, so hydrating only config/ before the push needs either a full pull first or a per-path conflict check.

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

Shipped

10/7/2026, 10:20:07 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack7210/7/2026, 7:36:29 PM
stack72 linked sibling of #316210/7/2026, 9:10:15 PM

Sign in to post a ripple.