deprecation: delete backups when they are deleted #3679
Merged
+44
−25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
General Checklist
Database Migrations
Deleted backups remain in the API DB, though there is no method of recovering from a backup that is deleted. It makes little sense to retain backups that are deleted in this case.
This announces the deprecation of deleted backups, and includes a migration that will remove deleted backups from the database.
Additionally, the
includeDeleted
option when querying backups will now do nothing, this will be removed in a future release.