Feature Request: add a "Clear all queues" context menu option for Azurite (or emulator) queues

[codywilliamson]

Preflight Checklist

• [X] I have installed the latest version of Storage Explorer.
• [X] I have checked existing resources, including the troubleshooting guide and the release notes.
• [X] I have searched for similar issues.

Problem

When using Azurite or any other emulated service for local development, there might be a lot of test data created. I find myself manually deleting a lot of queue items across several queues.

Desired Solution

It would be helpful to be able to right-click an emulator's entire queue and clear all messages

Alternatives and Workarounds

Manually clear all messages from each queue (possibly deleting generated data files, but haven't tested this)

Additional Context

No response

[MRayermannMSFT]

Hi @codywilliamson for this scenario we would recommend you go with deleting the Azurite data files to accomplish what you are looking for.

The files/folders Azurite uses to track queue data appear to be:

• azurite_db_queue folder
• azurite_db_queue.json

• __azurite_db_queue_extent__.json

  You should be able to just delete those from your Azurite folder. That will delete all queue related data. Alternatively if you want to simply go back to the state of "having a bunch of queues but none with messages", you could probably do something like:

1. Start Azurite
2. Create queues such that you are in the desired "having a bunch of queues but none with messages" state
3. Copy and paste the queue data files/folders somewhere else in order to backup that state
4. Do your work until you get to the point of wanting to restore back to the "having a bunch of queues but none with messages" state
5. Stop Azurite
6. Delete the queue data files/folders in your Azurite folder
7. Copy and paste the backup files/folder you created in step 3 back into your Azurite folder

Does that make sense?

[codywilliamson]

That's a great workaround and I can build some scripts that do this for me. I was more so hoping for a built-in way to do this, but thank you for the direction!

[MRayermannMSFT]

I was more so hoping for a built-in way

Understood. For now this sounds like a pretty niche feature, and one which has the potential to accidentally cause someone a lot of headache if they don't know what they are doing. So for now the self-scripted solution is what we'll recommend. We'll leave this open in our future milestone in case others come along wanting it as well.