Azure-storage-azcopy: How to list files to operate [ dry-run flag]
Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
10.1.2
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
azcopy copy/sync
What problem was encountered?
I cannot find the /L option of previous version. The '/L option' was used to list files to operate
How can we reproduce the problem in the simplest way?
run azcopy copy/sync
Have you found a mitigation/solution?
no
zelon
All 13 comments
Hi @zelon, thanks for reaching out!
To clarify, are we talking about a dry-run flag? For example, the files to be transferred are listed first without doing any actual work.
If yes, we have this feature on our backlog and will get to it shortly. If not, please let us know. Thanks!
zezha-msft
on 1 Jun 2019
yes, I want the 'dry-run' flag. I'm looking forward to the work. Thanks!
zelon
on 1 Jun 2019
@zelon sounds good! We'll update this thread once the work is scheduled.
zezha-msft
on 2 Jun 2019
Especially for rm with include / exclude flags this seems like a must-have feature.
Fuco1
on 9 Nov 2019
Yes. Especially for the sync operation. Ideally the results stored in the log file would be easily parsable so that the list of adds/deletes/overwrites could be pulled out and used pro grammatically if required
Thanks
Ed
eoq
on 19 Jan 2020
Hey, any progress on this front? It's still relevant for people in my company, we've wiped some data a bunch of times :blush: (so far we had backups, but...)
Fuco1
on 11 Sep 2020
Currently this is not a primary focus for us, but it is still on our radar. I'm sorry to hear that the lack of it is continuing to cause you trouble.
adreed-msft
on 12 Sep 2020
This would be an important story for backup and disaster recovery scenarios. --dry-run should be available for testing prior to running in an environment to prevent data loss.
asears
on 21 Oct 2020
Currently this is not a primary focus for us, but it is still on our radar. I'm sorry to hear that the lack of it is continuing to cause you trouble.
Any update on this?
hoshy
on 24 Nov 2020
Sorry for the delay, I will bring this issue up for prioritization with the team. Thanks.
zezha-msft
on 15 Dec 2020
Hi, this would be a great feature to have, similar to how rclone --dry-run flag works - good for testing before writing a new script.
mahalel
on 10 Jan 2021
How can it be that there seems to be no --dryrun flag for copying files and this issue is open since almost two years? You'd assume such basic functionality is included from the very beginning.
olastor
on 21 Feb 2021
Hi, any update on this? What was the feedback from the team when this was brought up in December?
espenairmine
on 23 Apr 2021
Related issues
martinwoodward
路
6Comments
amishra-dev
路
5Comments
alvipeo
路
4Comments
AMoghrabi
路
5Comments
Icybiubiubiu
路
4Comments
Most helpful comment
How can it be that there seems to be no
--dryrunflag for copying files and this issue is open since almost two years? You'd assume such basic functionality is included from the very beginning.