Sync overrides the container during the first run about azure-storage-azcopy HOT 5 CLOSED

@prjain-msft this is per the design. There were pre-existing files in the container.. Then wanted to copy a completely new folder to the container using sync command.. And of course all files in the container which did not exist in the local filesystem got deleted... This is per design... But users won't know this design until after they lose their data. Bottom line, can we have a warning, or a yes/no question before we do what we do (delete files in the destination that does not exist in source) ?

from azure-storage-azcopy.

For the first time, when you ran the sync command, how many files were there in you container aktest before running the sync command.

from azure-storage-azcopy.

We can do that. Print a warning message and ask for you user decision to delete the existing blobs or not.
I will add the task and work on it. But will this question be by default printed for every sync operation or will be printed only if there are existing blobs in the destination ?

from azure-storage-azcopy.

Possibly this would only be required if no files/folders from the source existed in the destination? Or perhaps this could be a flag --prompt-delete=true <default=false> If you have scripts that utilize azcopy it would be very annoying for them to be held up by a prompt.

from azure-storage-azcopy.

This is now fixed.

from azure-storage-azcopy.