-
Notifications
You must be signed in to change notification settings - Fork 3.4k
az storage azcopy blob changes underscores to dashes. #28868
Copy link
Copy link
Open
Labels
Auto-AssignAuto assign by botAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamStorageaz storageaz storageact-codegen-extensibility-squadpotential-pruningquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone
Metadata
Metadata
Labels
Auto-AssignAuto assign by botAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamStorageaz storageaz storageact-codegen-extensibility-squadpotential-pruningquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Describe the bug
az storage azcopy blob seems to be changing underscores in our destination name to dashes. This causes issues for some files that must adhere to certain naming schemes (such as CLI extensions).
Related command
We were using this: az storage azcopy blob upload --account-name $DESTINATION_STORAGE_ACCOUNT_NAME -c "cli-extension" -s "./$DESTINATION_FILE_NAME" -d "$DESTINATION_FILE_NAME" --output table --debug
But had to switch to this because the underscores in DESTINATION_FILE_NAME were being changed:
az storage blob upload --account-name $DESTINATION_STORAGE_ACCOUNT_NAME -c "cli-extension" --output table --name "$DESTINATION_FILE_NAME" --file "./$DESTINATION_FILE_NAME" --debug
Errors
No error, file name is changed.
Issue script & Debug output
See other entries
Expected behavior
No change to the name of the file we pass in.
Environment Summary
This happened during EV2 pipeline using this image:
"imageName": "adm-ubuntu-2004-l",
"imageVersion": "v5"
Additional context
No response