PPY-67: Added --no-cleanup
flag to neptune sync
to prevent cleanup of local logs after synchronization
#1892
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.
The current
neptune sync
architecture expects all containers to be synced to be moved to theasync
folder. Once the containers are synced, the local logs are deleted.This change adds a
--no-cleanup
flag toneptune sync
to prevent cleanup of local logs after synchronization,even though the logs will be moved to theasync
folder.Running
neptune sync --no-cleanup
again deletes the local logs of already synced containers anyway from theasync
folder. Need help figuring this out (not a priority)Before submitting checklist