← 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
dataOutputOverridesentry acceptsvaultName:DataOutputOverrideSchemainsrc/domain/models/data_output_override.tsincludes it, andStepSchemavalidates against that schema. Step.fromData(src/domain/workflows/step.ts) rebuilds each override fromspecName,lifetime,garbageCollection,tagsandvaryonly, sovaultNameis discarded.Step.toDatadrops it too.execution_service.tsandvalidation_service.tsreadstep.dataOutputOverrides, so a step-levelvaultNamenever routes sensitive outputs. The run uses the spec, default or first vault instead, with no error or warning.resolveSensitiveOutputVaultinsrc/domain/models/sensitive_output_vault.tsdocuments a workflow step'sdataOutputOverridesas a source ofvaultName.
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
Shipped
Click a lifecycle step above to view its details.
03Sludge Pulse
Sign in to post a ripple.