Lock snapshot during restore operation #1615
Merged
Conversation
This file contains 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
The snapshot is locked on the backend during the restore but the UI needs to wait until the next refresh to receive this status change. To provide better user experience we can lock the snapshot right after restore is triggered. The next refresh will confirm or clear the status (according to restore operation progress).
|
All tests passed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is follow-up to PR #1594
The snapshot is locked on the backend during the restore but the UI
needs to wait until the next refresh to receive this status change.
To provide better user experience we can lock the snapshot right
after restore is triggered. The next refresh will confirm or clear
the status (according to restore operation progress).