-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
max_backup_count should keep valid backups #607
Labels
help-wanted
Issues in the state 'help-wanted'
Comments
adejanovski
added
in-progress
Issues in the state 'in-progress'
and removed
ready
Issues in the state 'ready'
labels
Mar 27, 2024
adejanovski
added
ready-for-review
Issues in the state 'ready-for-review'
and removed
in-progress
Issues in the state 'in-progress'
labels
Mar 28, 2024
adejanovski
added
review
Issues in the state 'review'
and removed
ready-for-review
Issues in the state 'ready-for-review'
labels
Mar 29, 2024
This was referenced Apr 3, 2024
adejanovski
added
in-progress
Issues in the state 'in-progress'
and removed
review
Issues in the state 'review'
labels
Jun 13, 2024
adejanovski
added
review
Issues in the state 'review'
and removed
in-progress
Issues in the state 'in-progress'
labels
Jun 13, 2024
I've followed up on @adejanovski 's review and reimplemented the solution in a meaningfully simpler way. |
adejanovski
added
help-wanted
Issues in the state 'help-wanted'
and removed
review
Issues in the state 'review'
labels
Aug 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Project board link
If for any reasons your backups fails, the
medusa purge
task will delete what you have configured inmax_backup_count
, without taking the status in account.So you can end up with only incompletes backups:
max_backup_count = 5
:In this case, we don't have any valid backup due to the purge, only incomplete ones.
We may be able to keep
max_backup_count
valid backups after a purge. Not sure how to implement that btw.Yes I know, the real solution is to avoid failed backups :D
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: MED-26
The text was updated successfully, but these errors were encountered: