refactor(vmsync): extract SyncStrategy pattern for static state sync
#4652
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.
Why this should be merged
Check #4651
How this works
Restructure the
vmsyncpackage to separate concerns and prepare for future dynamic state sync support.finalizer.go- VM state finalization logic (finishSync,commitMarkers) moved to dedicatedfinalizerstruct.SyncStrategyinterface withStartmethod for sync execution.staticStrategyfor current sequential sync behavior.client.goto orchestrate sync lifecycle via strategy.This refactoring enables adding dynamic state sync as a separate strategy implementation without modifying existing static sync logic.
How this was tested
existing UT
Need to be documented in RELEASES.md?
no
resolves #4651
Signed-off-by: Tsvetan Dimitrov (tsvetan.dimitrov@avalabs.org)