Feature/persisted state archive export on change #1190
Closed
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
…e on change of some data to persistence
zan-mateusz
force-pushed
the
feature/persisted-state-archive-export-on-change
branch
from
34aed00 to
607930d
Compare
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.
WIP
Automated capture of persisted state into an archive saved in the root persistence directory - invoked on persistence change.
Archive is of hardcoded name 'persistence-state-export.zip' and is saved in the root or persistence directory. In case a new one is generated, old one is removed so we keep only the most up to date version of the export.
This is applicable only to file based persistence stores