Add snapshot-based rollback backup step in db/migrate.ts - #798
Open
lauferuqquyah wants to merge 1 commit into
Open
Add snapshot-based rollback backup step in db/migrate.ts#798lauferuqquyah wants to merge 1 commit into
lauferuqquyah wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This change introduces an automated snapshot-based backup step before running destructive database migrations. Before any migration that may modify or remove existing data is executed, the migration process requests a logical database snapshot from the configured provider.
If the snapshot is created successfully, the snapshot ID is recorded in the audit log and the migration proceeds. If the snapshot request fails, the migration is aborted to prevent potential data loss.
This enhancement improves the reliability and safety of the migration process by ensuring a recovery point is available before destructive schema changes are applied.
Closes #572