End-to-end pipeline drill (synthetic alert injection) #86
Labels
No labels
area:ai
area:ci-cd
area:notifications
area:observability
area:public-pages
backlog
bug
duplicate
enhancement
help wanted
invalid
question
type:decision
type:feature
type:infra
type:maintenance
type:security
v1.0.1
v1.1.0
v1.2.0
v1.3.0
v2.0.0
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/WeatherBot#86
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Beyond the existing per-channel test button: inject a synthetic NWS alert for a chosen location and watch it flow through matching
Filed from the 2026-07-17 codebase audit (
docs/.internal/report-2026-07-17.md), finding I-16.Done in #101 (merged). Admin-only
POST /api/diagnostics/pipeline-drill(CSRF-protected) injects a synthetic "Pipeline Drill (TEST)" alert (unique id, 10-min expiry, matched to a target location's own zone) through the real_process_single_alertpath — creatingSentAlert+ delivery-outbox rows and dispatching to configured channels — and returns a summary (zone/severity match, matched channels, per-channel delivery outcomes).dry_run=truematches without creating rows or dispatching. Non-dry runs send real messages, so the event is clearly marked TEST and self-clears via the short expiry.