Skip to content
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

When migrations go wrong there should be an option to roll back to your prior state? #301

Open
Connoropolous opened this issue Jul 4, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@Connoropolous
Copy link
Collaborator

No description provided.

@Connoropolous
Copy link
Collaborator Author

cc @zippy
will try to tackle on this this month

@Connoropolous Connoropolous self-assigned this Jul 29, 2023
@Connoropolous Connoropolous changed the title When migrations go wrong, or get stuck, there should be error handling, rollbacks, and better strategies for dealing with it. When migrations go wrong there should be an option to roll back to your prior state? Aug 10, 2023
@Connoropolous
Copy link
Collaborator Author

another way to approach this is to say that the whole migration should be:
step 1: prepared
step 2: committed

If anything goes wrong during the preparation that's fine. Eject.

Make step 2 one holistic update that either succeeds or fails all at once, so that it's atomic. And then again, if anything goes wrong, it just safely ejects.

@pegahvaezi pegahvaezi added the bug Something isn't working label Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants