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

Relationships

#536 fix: datastoreSetupExtension() ignores namespace config on initial migration push/pull

Opened by stack72 · 6/3/2026· Shipped 6/3/2026

Description

datastoreSetupExtension() in src/libswamp/datastores/setup.ts has the same missing-namespace bug as #534. When swamp datastore setup runs against a namespace-scoped config, the initial migration push/pull ignores the namespace field and operates on the global index instead of the per-namespace index.

Same pattern as #534 (fixed in PR #1497): the auto-sync path in repo_context.ts correctly threads namespace, but this setup path was missed.

Steps to Reproduce

  1. Configure a repo with namespace: infra and an S3 datastore
  2. Run swamp datastore setup extension @swamp/s3-datastore
  3. The initial migration push creates a global .datastore-index.json instead of infra/.datastore-index.json

Expected Behavior

The initial migration push/pull should respect the namespace config and use per-namespace index paths.

Impact

Low — datastore setup is a one-time operation and users aren't configuring namespaces via datastore setup yet (that requires Phase 7 migration commands). But this must be fixed before Phase 7 lands.

Fix

Same pattern as #534: thread namespace from config into the push/pull calls in datastoreSetupExtension(). Found during adversarial code review of #534.

  • #534 (same bug in swamp datastore sync, fixed)
  • #525 (Phase 6 core infrastructure)
  • #533 (S3/GCS extension namespace support)
02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 3 MOREPR_MERGED+ 1 MORENOTIFICATION_SKIPPED

Shipped

6/3/2026, 1:33:33 AM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack726/3/2026, 1:08:13 AM

Sign in to post a ripple.