hippogrief/pobsync
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

(feature) Add run completion notifications #68

Merged
parkel merged 1 commits from issue-50-run-notifications into master 2026-05-28 21:21:00 +02:00
Conversation 0 Commits 1 Files Changed 14 +819 -4
parkel commented 2026-05-28 21:20:55 +02:00
Owner
Copy Link

Summary

  • Add notification targets for email and webhooks.
  • Record notification deliveries per backup run and target.
  • Send notifications after completed, warning, failed, or cancelled runs.
  • Add a Django Notifications page for target management and recent deliveries.
  • Keep notification failures isolated from backup execution.

Tests

  • .venv/bin/python manage.py test src.pobsync_backend --verbosity 2
  • .venv/bin/python manage.py check
  • git diff --check
  • .venv/bin/python manage.py makemigrations --check --dry-run --verbosity 2

Closes #50

## Summary - Add notification targets for email and webhooks. - Record notification deliveries per backup run and target. - Send notifications after completed, warning, failed, or cancelled runs. - Add a Django Notifications page for target management and recent deliveries. - Keep notification failures isolated from backup execution. ## Tests - .venv/bin/python manage.py test src.pobsync_backend --verbosity 2 - .venv/bin/python manage.py check - git diff --check - .venv/bin/python manage.py makemigrations --check --dry-run --verbosity 2 Closes #50
parkel added 1 commit 2026-05-28 21:20:55 +02:00
(feature) Add run completion notifications 67ffd6101b 
Add email and webhook notification targets with delivery tracking, and send
notifications when backup runs reach a terminal status.

Expose notification target management in the Django UI and keep delivery
failures recorded without failing the backup worker.
parkel merged commit eb121453c8 into master 2026-05-28 21:21:00 +02:00
parkel deleted branch issue-50-run-notifications 2026-05-28 21:21:00 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
area: future
Longer-term product direction.
 area: observability
Metrics, history, and capacity insights.
 area: policy
Backup policies, templates, and automation.
 area: restore
Restore and recovery workflows.
 area: security
Permissions, audit, and security hardening.
 bugfix
Bug fixes and correctness work.
 docs
Documentation and operator guidance.
 feature
New functionality.
 refactor
Internal restructuring without direct behavior changes.
 release
Release preparation and publishing.
 security
Security, permissions, and audit work.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
parkel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hippogrief/pobsync#68
Delete Branch "issue-50-run-notifications"

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?