az storage blob directory is implicitly deprecated

[miyamam]

[Enter feedback here]
Document indicate this command is still preview but when I executed it shows the following message.
"This command is implicitly deprecated because command group 'storage blob directory' is deprecated and will be removed in a future release. Use 'az storage fs directory' instead."

Should we update Note comments?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 978a095c-3ead-282f-304f-fb627dad53a4
• Version Independent ID: 43fb2b4e-3f87-f3b8-2e85-ed5812a69ffc
• Content: az storage blob directory
• Content Source: latest/docs-ref-autogen/storage/blob/directory.yml
• Service: storage
• GitHub Login: @rloutlaw
• Microsoft Alias: routlaw

[yonzhan]

storage

[sjuarezgx]

I have the same doubt, is this command deprecated? The document says it's still in preview:
https://docs.microsoft.com/en-us/cli/azure/storage/blob/directory?view=azure-cli-latest#code-try-21

[eliasarellano]

Hello,
I have also the same doubt, I don't think that the az storage fs directory would be usefull, the container name is not part of the parameter, how can I precise it when I need to delete a directory from a container ?

[evelyn-ys]

@eliasarellano Please specify container name with --file-system:

[eliasarellano]

Hello again,
I tested the solution proposed by @evelyn-ys and this worked with my storage account for testing purposes, but not with the other one.

The error that I got is this one:

ERROR: cli.azure.cli.core.azclierror: (EndpointUnsupportedAccountFeatures) This endpoint does not support BlobStorageEvents or SoftDelete. Please disable these account features if you would like to use this endpoint.

I didn't understand this issue, the code was this one.

$accountKey = az storage account keys list --account-name $HubStorageAccount --query [0].value -o tsv

az storage fs directory delete --file-system $HubStorageContainer --account-name $HubStorageAccount --account-key $accountKey --name $storageProjectFolder --yes --debug

So then I tried to do the same with AzPowershell, and the result was good with all the storage accounts that I checked.

$azkey = Get-AzStorageAccountKey -ResourceGroupName "my-resourcegroup" -AccountName $HubStorageAccount
$ctx = New-AzStorageContext -StorageAccountName $HubStorageAccount -StorageAccountKey $azkey[0].value            
$values = Get-AzStorageBlob -Container $HubStorageContainer -Blob "$storageProjectFolder/*" -Context $ctx.Context

foreach($val in $values){Remove-AzStorageBlob -Container $HubStorageContainer -Blob $val.Name -Context $ctx.Context }

In this last code, as you see I listed all the blobs, and then deleted them one by one, until that the folder is empty, so completely removed.

Any tips for AZ cli? I didn't need to modify the properties of the storage accounts to make AzPowershell work.
For azcli, even for listing blobs it propose me to change to az storage fs instead of az storage blob.

[kjoth]

Hi @evelyn-ys Could you confirm, is this command "az storage blob directory delete" deprecated or can be used ?

[evelyn-ys]

It's deprecated

[jjgriff93]

@evelyn-ys - documentation is quite misleading here. No mention of it being deprecated and it's still in "preview" - also no pointers to the fs command instead, and the fs command explicitly states it's for ADLS Gen2 filesystems even though it can also be used with blob

[erorubrz]

Having this issue even today..