Relationships
↔ sibling #4588#4560 serve: reload installs trigger overrides from serve.yaml without validating them
Opened by zack · 11/9/2026· Shipped 11/10/2026
Problem
A reload (SIGHUP or swamp serve reload) reads serve.yaml through readServeConfigFile in src/serve/serve_config.ts, which only parses the YAML. performServeReload (src/serve/extension_reload.ts) then passes config.triggers straight to the trigger override updater without running validateTriggerOverrideEntry, which boot and swamp serve check-config apply (entry is a mapping, schedule is a valid cron expression, inputs is a mapping, catchUp parses and needs schedule, at least one of schedule or inputs). A non-mapping triggers value is also not checked.
So an override serve would refuse at boot, such as an invalid cron expression, can be installed by a reload, failing later in a less clear way.
Expected
A reload validates trigger overrides exactly as boot does and, on a refusal, keeps the previous overrides and reports the reason.
Notes
Found while triaging swamp-club#4550, which covers the same gap for webhook entries.
Shipped
Click a lifecycle step above to view its details.
Sign in to post a ripple.