Need ability to clear all storage

Which service(blob, file, queue, table) does this issue concern?

All

Which version of the Azurite was used?

3.8.0

Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)

npm

What’s the Node.js version?

12.18.4

What problem was encountered?

I need to be able to clear storage like I could with Azure Storage Emulator using clear all, clear blob, etc.

Steps to reproduce the issue?

I’m working off the output from -h - it says nothing about the ability to do this.

Have you found a mitigation/solution?

No, I am new to Azurite so I’m unsure if there’s some “hack” you can do to effectively do this.

Use case: When developing with a technology like Durable Functions, which heavily utilizes queues, tables, and blob to maintain state of orchestrations it’s incredibly useful to be able to clear backend storage contents as a way to “restart” an orchestration debugging session.

[brandonh-msft]

I’m fine if you want to propose that as a temporary workaround but not the permanent solution.

1. It’s not affordable outside this work item - people would have to come find this to find that script line, nobody’s going to discover that on their own
2. It’s not obvious what’s being done if you were to embed this in a script somewhere; you’d have to comment the line to point out what you’re doing here and why
3. It’s not cross-platform except and unless somebody installs Powershell Core on their box, which shouldn’t be a prereq for using Azurite.

So what I’m saying is thanks, and I’ll use that if/when I get back to having Azurite as part of my daily dev workflow (I’ve moved on from Functions/DF work) but would much rather see something I can discover & interpret from azurite -h than a separate script I pulled from the bowels of the internet 😉

[codermrrob]

It is correct that the ability to clear or clean the storage while developing durable functions is really necessary. It is laborious to rely on deleting files - I must quit from Visual Studio before I can delete them, restart VS and run my durable functions and then repeat for every debug session. It’s a poor workflow.

I have also tried using the VSCode durable function plugin to delete the hub (nothing else seemed to work) but it is somewhat slow compared to previous CLI command for the old storage emulator.

I appreciate this is an open source project and if I find time I will do something about it. For now I just want to draw attention to this area, that for developers working a lot on durable functions Azurite breaks our development workflow in comparison with the old storage emulator.