You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #680, someone introduced a way to get the link by pattern https://azcopyvnext.azureedge.net/releaseyyyymmdd/azcopy_linux_amd64_XX.YY.Z.tar.gz. But the trickiest part is the release date has some skew so there might be some guess.
So, it will be great if the official doc can provide a user-friendly permanent links.
Some possible approaches
Allow anonymous listing for https://azcopyvnext.azureedge.net/, so that users can browse to get the desired version.
Always provide static links on Github release page. Actually, a few releases provided such links while most were not.
Summarize a list of historical versions on github repo or MS docs.
Use a 100% predictable link pattern for https://azcopyvnext.azureedge.net/***
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?
The text was updated successfully, but these errors were encountered:
konjac
changed the title
Permanent download link for versions
Permanent download link for specific versions
Jun 26, 2024
Which version of the AzCopy was used?
All
Which platform are you using? (ex: Windows, Mac, Linux)
What command did you run?
What problem was encountered?
It is a common scenario to use a static version for azcopy. Production upgrade usually needs careful validation.
The doc https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10#obtain-a-static-download-link shares how to get the static download link of the current
aka.ms/downloadazcopy-v10-**
. However, it is now easy for a previous version.In #680, someone introduced a way to get the link by pattern
https://azcopyvnext.azureedge.net/releaseyyyymmdd/azcopy_linux_amd64_XX.YY.Z.tar.gz
. But the trickiest part is the release date has some skew so there might be some guess.So, it will be great if the official doc can provide a user-friendly permanent links.
Some possible approaches
https://azcopyvnext.azureedge.net/
, so that users can browse to get the desired version.https://azcopyvnext.azureedge.net/***
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?
The text was updated successfully, but these errors were encountered: