Allow users to manage backup retention and backup logs
- Dominant language
- Python
- Stars
- 562
- Forks
- 410
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 197
Description
**Mandatory**
- Keep site backup logs on press irrespective of status / cleanup actions
**Additional**
- Allow users to configure backup retention
- Like keep all backups of 1 year, 2 year (instead of purging based on grandfather-father-son algo)
- Charge customers for the additional backups
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating the existing backup cleanup, log retention, and grandfather-father-son logic, then trace how retention settings and backup storage costs could connect to customer billing; done means logs survive cleanup and status changes, configurable retention periods work, and additional backups are chargeable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100