Relationships
#4549 serve: optionally poll the webhook route directory so a deploy alone makes routes live
Opened by zack · 11/9/2026· Shipped 11/9/2026
Problem
Once webhook routes can live in repo files (#4547), making a new route live still needs someone to run swamp serve reload on the host after each deploy. The config poller (src/serve/config_poller.ts) does not re-read webhooks today; its extension reload explicitly skips them.
Proposed solution
Add optional polling of the route directory, so deploying the change is enough. When the files change, serve applies the change through the same path as swamp serve reload (src/serve/webhook_reload.ts). That means the same validation, the same clash and shadowing rules, and the same refusal of literal secrets.
- Off by default. Turned on by a serve config option (name to settle in triage) and set at startup.
- A file that fails to load keeps the last good set of routes running and reports the error in health. It does not take down routes that were working.
- Each change applied by polling is audited and shows in health with its
file:<name>source, the same as a manual reload. - Vault-backed secrets are resolved again when a route changes, as on reload.
Why it's separate
Polling lets a route go live without anyone running a command. It is optional in the proposal, so it can be deferred without blocking #4547.
Depends on
#4547
Shipped
Click a lifecycle step above to view its details.
Sign in to post a ripple.