I have a blob container in Azure called pictures
that has various folders within it (see snapshot below):
I\'m trying to delete the folders tit
There is also a desktop storage explorer from Microsoft. It has a feature where you can select the virtual folder and then delete it effectively deleting all sub blobs.
https://azure.microsoft.com/en-us/features/storage-explorer/
You can also do it in Azure cloud shell; here is the command:
az storage blob delete-batch --source <blob-container> --account-name <blob-account> --pattern <folder-name>*
In the latest repo, Azure.Storage.Blobs, it's very straightforward
var connectionString = "blob-connection-string";
var containerName = "container-name";
var folderPath = "folder1/subfolder/sub-subfolder";
var blobServiceClient = new BlobServiceClient(connectionString);
var blobContainerClient = blobServiceClient.GetBlobContainerClient(containerName);
var blobItems = blobContainerClient.GetBlobsAsync(prefix: folderPath);
await foreach (BlobItem blobItem in blobItems)
{
BlobClient blobClient = blobContainerClient.GetBlobClient(blobItem.Name);
await blobClient.DeleteIfExistsAsync();
}
As every blob has its own uri value, you can set prefix before querying so that it can fetch and delete blobs with the particular uri. The folder will disappear as the blobs get deleted.
Windows Azure Blob Storage does not have the concept of folders. The hierarchy is very simple: storage account > container > blob. In fact, removing a particular folder is removing all the blobs which start with the folder name. You can write the simple code as below to delete your folders:
CloudStorageAccount storageAccount = CloudStorageAccount.Parse("your storage account");
CloudBlobContainer container = storageAccount.CreateCloudBlobClient().GetContainerReference("pictures");
foreach (IListBlobItem blob in container.GetDirectoryReference("users").ListBlobs(true))
{
if (blob.GetType() == typeof(CloudBlob) || blob.GetType().BaseType == typeof(CloudBlob))
{
((CloudBlob)blob).DeleteIfExists();
}
}
container.GetDirectoryReference("users").ListBlobs(true) lists the blobs start with "users" within the "picture" container, you can then delete them individually. To delete other folders, you just need to specify like this GetDirectoryReference("your folder name").
Its because the "folders" don't actually exist. In an Azure storage account, you have containers which are filled with blobs. What you see visualized by clients as "folders" are the file names of the blobs in the account "pictures/uploads/". If you want to remove the "folder", you actually have to remove each of the blobs that are named with the same "path".
The most common approach is to get a list of these blobs then feed that to the delete blob call.
Let's start with an example how to delete a "folder" using ListBlobsSegmentedAsyc:
var container = // get container reference
var ctoken = new BlobContinuationToken();
do
{
var result = await container.ListBlobsSegmentedAsync("myfolder", true, BlobListingDetails.None, null, ctoken, null, null);
ctoken = result.ContinuationToken;
await Task.WhenAll(result.Results
.Select(item => (item as CloudBlob)?.DeleteIfExistsAsync())
.Where(task => task != null)
);
} while (ctoken != null);
What it does...
var ctoken = new BlobContinuationToken();
A "folder" may contain a lot of files. ListBlobSegmentedAsyc may return only a part of them. This token will store the info where to continue in next call.
var result = await container.ListBlobsSegmentedAsync("myfolder", true, BlobListingDetails.None, null, ctoken, null, null);
For all arguments see https://docs.microsoft.com/en-us/dotnet/api/microsoft.windowsazure.storage.blob.cloudblobclient.listblobssegmentedasync?view=azure-dotnet for details.
(item as CloudBlob)?.DeleteIfExistsAsync()
Now we have a list of IListBlobItem in result.Results. Because an IListBlobItem is not guaranteed to be a deletable CloudBlob (e.g. it could be a virtual folder if we would have set useFlatBlobListing=false), we try to cast it and delete it if possible.
result.Results.Select(item => (item as CloudBlob)?.DeleteIfExistsAsync())
Triggers delete for all results and returns a list of tasks.
.Where(task => task != null)
If Results contained items we could not cast to CloudBlob, our list of tasks contains null values. We have to remove them.
... then we wait until all delete for current segment finished and continue with next segment if available.