Fix silent failures with leading slash or no name virtual dirs #3294
+253
−2
Conversation
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
wonwuakpa-msft
changed the title
//blob
wonwuakpa-msft
changed the title
//blob
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
With un-named virtual directories or blob with leading slashes e.g
//blob, AzCopy normalizes the path and that led to 404 BlobNotFound error that we are now catching. If the user wants to successfully copy from an unnamed virtual directory with --list-of-files, the correct syntax ishttps://acct.blob.core.windows.net/cont//without the trailing wildcard.Feature / Bug Fix: (Brief description of the feature or issue being addressed)
Related Links:
PBI Item
Team thread
Type of Change
How Has This Been Tested?
Thank you for your contribution to AzCopy!