Recursive bucket sync and delete actions#231
Merged
Conversation
Coverage Report (Application)
|
Coverage Report (Frontend)
|
TimCsaky
force-pushed
the
sync-on-connect
branch
from
df08f0e to
b32041a
Compare
TimCsaky
force-pushed
the
sync-on-connect
branch
from
b32041a to
c0136e5
Compare
norrisng-bc
approved these changes
Apr 2, 2025
TimCsaky
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Trigger recursive sync when connecting a new storage location
Do a recursive delete when deleting a folder (bucket)
this will require COMS pr 297 to be merged first)
Types of changes
New feature (non-breaking change which adds functionality)
Checklist
Further comments