feat(backup): Add backup scheduling system with GFS retention, API and UI integration
This commit is contained in:
12
changelog.md
12
changelog.md
@@ -1,5 +1,17 @@
|
||||
# Changelog
|
||||
|
||||
## 2025-11-27 - 1.8.0 - feat(backup)
|
||||
Add backup scheduling system with GFS retention, API and UI integration
|
||||
|
||||
- Introduce backup scheduling subsystem (BackupScheduler) and integrate it into Onebox lifecycle (init & shutdown)
|
||||
- Extend BackupManager.createBackup to accept schedule metadata (scheduleId) so scheduled runs are tracked
|
||||
- Add GFS-style retention policy support (IRetentionPolicy + RETENTION_PRESETS) and expose per-tier retention in types
|
||||
- Database migrations and repository changes: create backups and backup_schedules tables, add schedule_id, per-tier retention columns, and scope (all/pattern/service) support (migrations up to version 12)
|
||||
- HTTP API: add backup schedule endpoints (GET/POST/PUT/DELETE /api/backup-schedules), trigger endpoint (/api/backup-schedules/:id/trigger), and service-scoped schedule endpoints
|
||||
- UI: add API client methods for backup schedules and register a Backups tab in Services UI to surface schedules/backups
|
||||
- Add task scheduling dependency (@push.rocks/taskbuffer) and export it via plugins.ts; update deno.json accordingly
|
||||
- Type and repository updates across codebase to support schedule-aware backups, schedule CRUD, and retention enforcement
|
||||
|
||||
## 2025-11-27 - 1.7.0 - feat(backup)
|
||||
Add backup system: BackupManager, DB schema, API endpoints and UI support
|
||||
|
||||
|
||||
Reference in New Issue
Block a user