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

Relationships

#2067 Enrich InvocationContext telemetry with datastore type and external vault detection

Opened by stack72 · 9/8/2026· Shipped 9/8/2026

Problem

Identifying users enabling external datastores or vaults requires piecing together various telemetry events. The InvocationContext (stamped on every CLI invocation) has an externalDatastoreConfigured boolean but:

  1. No vault equivalent — there is no externalVaultConfigured field. The only way to know someone uses an external vault is to find a historical vault create command invocation and correlate by repo.
  2. No datastore type — the boolean tells you whether an external datastore is configured, but not which type (S3, GCS, Azure, custom extension).

Proposed Solution

Two additions to InvocationContext in src/domain/telemetry/invocation_context.ts:

  1. datastoreType: string | undefined — propagate marker.datastore.type (already available on the repo marker) into the invocation context. Turns the bare boolean into actionable signal.

  2. externalVaultConfigured: boolean — derived by scanning the vault configs directory at CLI init time and checking for any vault with type !== "local_encryption". The scan reads a handful of small local YAML files — negligible cost.

Both flow through the existing telemetry pipeline with no new events needed. Every CLI invocation would automatically carry the richer context.

Alternatives

  • Marker-cached vault types: write a vaultTypes summary to .swamp.yaml at vault create/vault delete time. Avoids the directory scan but adds write-time bookkeeping and a migration. The scan is simpler and always accurate.
  • Dedicated events: emit separate "vault configured" / "datastore configured" events. Overkill — the invocation context already reaches every telemetry entry.
02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 9 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

9/8/2026, 7:46:48 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack729/8/2026, 5:52:30 PM

Sign in to post a ripple.