Skip to content

feat: auto-disarm cloud alerts after firing#265

Merged
elsbrock merged 2 commits intomainfrom
fix/264-cloud-alert-auto-disarm
Mar 24, 2026
Merged

feat: auto-disarm cloud alerts after firing#265
elsbrock merged 2 commits intomainfrom
fix/264-cloud-alert-auto-disarm

Conversation

@elsbrock
Copy link
Copy Markdown
Owner

Summary

  • Cloud availability alerts now auto-disarm after firing to prevent continuous notifications (fixes Cloud availability alerts should auto-disarm after firing #264)
  • Add is_armed column to cloud_availability_alert table (migration 0013)
  • Worker only fetches armed alerts (WHERE is_armed = 1) and disarms them in the same batch as recording triggers
  • API supports re-arming alerts via PATCH /cloud-alerts/:id with { isArmed: true }
  • UI shows "Disarmed" badge and a re-arm button for fired alerts

Test plan

  • npm run check passes (0 errors, 0 warnings)
  • npm run test passes (33 tests)
  • npm run lint passes (0 errors)
  • Worker tests pass (188 tests) — updated fixtures and assertions for is_armed
  • After deploying migration 0013, verify existing alerts default to is_armed = TRUE
  • Verify that when a cloud alert fires, it gets disarmed and shows "Disarmed" badge in UI
  • Verify re-arm button works and alert starts monitoring again

https://claude.ai/code/session_01KgBxH5WppN5k7houNonsf8

claude added 2 commits March 24, 2026 12:37
Cloud availability alerts now automatically disarm after firing to
prevent continuous notifications. Users can re-arm alerts at any time
from the alert management page.

Changes:
- Add `is_armed` column to cloud_availability_alert (migration 0013)
- Worker only fetches armed alerts and disarms them after firing
- API supports re-arming via PATCH with isArmed: true
- UI shows disarmed state with badge and re-arm button
- Update descriptions to reflect new behavior

Fixes #264

https://claude.ai/code/session_01KgBxH5WppN5k7houNonsf8
CI uses `lts/*` which now resolves to Node 24 (npm 11), but the
lockfile was generated with Node 22 (npm 10). npm 11 has stricter
peer dependency handling and rejects the lockfile.

Pin all workflows to Node 22 (Maintenance LTS until Apr 2027) to
match the development environment.

https://claude.ai/code/session_01KgBxH5WppN5k7houNonsf8
@elsbrock elsbrock enabled auto-merge (squash) March 24, 2026 13:22
@elsbrock elsbrock disabled auto-merge March 24, 2026 14:04
@elsbrock elsbrock merged commit 2aef50a into main Mar 24, 2026
5 of 6 checks passed
@elsbrock elsbrock deleted the fix/264-cloud-alert-auto-disarm branch March 24, 2026 14:04
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.

Cloud availability alerts should auto-disarm after firing

2 participants