Skip to main content
← Back to list
01Issue
FeatureIn ProgressSwamp CLI
Assigneesstack72

Relationships

#1648 Trigger overrides: observability and cleanup follow-ups

Opened by stack72 · 8/14/2026

Follow-ups from PR #2144 review feedback.

Observability (CLI UX Review)

  1. Startup log confirming overrides loaded — Add a line like Loaded N trigger override(s) from serve.yaml after Boot: starting scheduler so users know the config was read without waiting for schedule_registered logs.

  2. Distinguish override from built-in in schedule loghandleScheduleChange logs Registered schedule for workflow {name}: {schedule} for both cases. Add (serve.yaml override) qualifier when resolveSchedule chose the override.

  3. Warn on inputs-only override for unscheduled workflow — An override with only inputs (no schedule) on a workflow that has no built-in schedule is a silent no-op. Log a warning at the end of applyTriggerOverrides.

Cleanup (Code Review / Adversarial Review)

  1. Workflow.withTrigger() is unused in production — Defined and tested (6 tests) but not called in any production code path. Either wire it into #2142 (CLI commands) or remove until needed.

  2. withTrigger bypasses domain validation — Calls the private constructor directly, skipping cron validation. Safe today because serve_config.ts validates upstream, but fragile if called from unvalidated paths. Consider adding validation or documenting the contract.

  3. O(n) linear scan in applyTriggerOverrides[...this.workflowNames.values()].includes(workflowName) could use a reverse-index Set<string> for O(1) lookup. Negligible at realistic scale.

  4. Remove WHAT comment// Build trigger overrides map from serve config in serve.ts is self-explanatory.


Automoved by swampadmin from https://github.com/swamp-club/swamp/issues/2145

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 3 MOREPR_LINKED

In Progress

8/14/2026, 4:44:18 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack728/14/2026, 4:08:59 PM

Sign in to post a ripple.