Technical Thursday – Azure-Cli storage account bug has been fixed

About a month ago I wrote a post about a Bug in azure-cli 2.0.30. That bug affects some amaretto related functions and features. As I forecasted and the MS promised me the fix is here. This is a really good news. Today I will show you how this fix works then I provide a collection of affected materials of fix.

Update Azure-Cli to 2.0.32

First step is to update Azure-Cli to 2.0.32.

And please check the installed version of Azure-Cli on your machine.

 az --version

It’s great…Let’s test again the previous command.

Test copy

So now we can test again the command from the past:

az storage blob copy start --account-name mystorageacc --sas-token "?sv=2017-07-29&ss=bfqt&srt=sco&sp=rwdlacup&se=2019-04-04T15:43:14Z&st=2018-04-03T23:43:14Z&spr=https&sig=***************" --destination-container "files" --source-container "files" --source-blob "new/arm-template.json" --destination-blob "archive/arm-template.json" --source-account-name mystorageacc --source-sas "?sv=2017-07-29&ss=bfqt&srt=sco&sp=rwdlacup&se=2019-04-04T15:43:14Z&st=2018-04-03T23:43:14Z&spr=https&sig=***************" --debug

then cross your fingers to receive the required result:

{
  "completionTime": null,
  "id": "fb833d2e-945e-42ca-98f0-b77dfa60f145",
  "progress": null,
  "source": null,
  "status": "success",
  "statusDescription": null
}

Yes! It works.

 

Result and conclusion

As you can see it works again so you can continue your work with SAS Tokens.

Additionally please keep in your mind this fix affects the following materials:

 

That’s all for Today. Sunshine and some good news. 🙂

Be the first to comment on "Technical Thursday – Azure-Cli storage account bug has been fixed"

Leave a comment