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

Relationships

#3606 Workflow step dataOutputOverrides vaultName is accepted but silently dropped

Opened by zack · 10/19/2026· Shipped 10/20/2026

Problem

  • A workflow step's dataOutputOverrides entry accepts vaultName: DataOutputOverrideSchema in src/domain/models/data_output_override.ts includes it, and StepSchema validates against that schema.
  • Step.fromData (src/domain/workflows/step.ts) rebuilds each override from specName, lifetime, garbageCollection, tags and vary only, so vaultName is discarded. Step.toData drops it too.
  • execution_service.ts and validation_service.ts read step.dataOutputOverrides, so a step-level vaultName never routes sensitive outputs. The run uses the spec, default or first vault instead, with no error or warning.
  • resolveSensitiveOutputVault in src/domain/models/sensitive_output_vault.ts documents a workflow step's dataOutputOverrides as a source of vaultName.

Expected

Either keep vaultName through Step.fromData and toData so it applies, or reject it at validation.

Related

The reference check that swamp vault remove adds for swamp-club#3597 does not scan step overrides, because they cannot name a vault today. If this is fixed by keeping vaultName, add step overrides to findVaultReferences in src/domain/vaults/vault_references.ts.

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

Shipped

10/20/2026, 5:56:25 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack7210/20/2026, 4:30:05 PM

Sign in to post a ripple.