Skip to content

feat: notification catalog and device notifications (v0.14.0) - #33

Merged
yakari007 merged 1 commit into
masterfrom
feat/device-notifications
Oct 12, 2026
Merged

yakari007 merged 1 commit into
masterfrom
feat/device-notifications

Conversation

@yakari007

Copy link
Copy Markdown
Contributor

Summary

  • GET /v1/notification-catalog: every notification a webhook can receive, with example payloads and route match fields.
  • GET /v1/devices/{device_id}/notifications: routes that take the device's incidents (matches_because, matched_checks), webhook delivery health, would_fire with a reason, and recent deliveries with payloads. Cursor paging, status and event_type filters. Routes and webhooks carry their external refs.
  • Migration 00025: webhook_delivery_devices, filled by a trigger and backfilled, so the device filter is an indexed lookup.

Test plan

  • TestDeviceNotifications (new) and the full go test ./... suite
  • go vet, gofmt
  • Backfill of existing deliveries not covered by a test

🤖 Generated with Claude Code

Add GET /v1/notification-catalog (every notification with an example
payload) and GET /v1/devices/{device_id}/notifications (matching routes,
webhook health, would_fire with a reason, recent deliveries with payloads,
external refs). Migration 00025 links deliveries to devices with a trigger
and a backfill so the device filter is an indexed lookup.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@yakari007
yakari007 merged commit 60fcc32 into master Oct 12, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant