gobackup / gobackup/gobackup-operator
[Verify] Scheduled test-restore (tested restores)
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 23
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Part of #81. Depends on #93, #94, #95.
Summary
Periodically restore the latest backup into an ephemeral throwaway database, optionally run validation queries, then tear it down — proving backups are practically recoverable ("tested restores").
Scope
- Scheduled test-restore config (on
Backupor a dedicated resource): cadence, ephemeral target provisioning, optional validation query, teardown. - Reuses the restore path; results feed status conditions + metrics.
Acceptance criteria
- On schedule, the latest backup is restored to an ephemeral DB, the validation query runs, and the target is torn down.
- Success/failure surfaced as conditions + metrics; failures alertable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the related work in #81 and dependencies #93, #94, and #95, then trace the existing restore path and the Backup or dedicated-resource configuration. Done means a scheduled restore uses the latest backup, runs the optional validation query, tears down the ephemeral database, and exposes success or failure through conditions and metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100