Event Hubs should allow reuse of an existing storage resource

[atrauzzi]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

When I add Event Hubs to my deployment and run the local emulator, I end up getting a storage container, even though I've already got one configured.

Describe the solution you'd like

It would be nice to be able to tell the Event Hubs local deployment to simply reuse my existing storage account for whatever it needs, and perhaps even with a prefix or an effective namespace/container of some kind?

Additional context

No response

[davidfowl]

You should treat the event hubs storage like an implementation detail of the emulator. Unfortunately, we only have a flat resource list without a hierarchy so it shows up. Is there another reason you want to share the storage resource with the event hubs implementation?

[atrauzzi]

Two reasons: Save on local dev memory, but also to be able to have the same visibility of everything all in one spot.

But yeah, if this approach becomes the norm in Aspire, I could see memory use going out of control. That's my bigger concern.

[buzzaII]

Service Bus emulator will have the similar concerns as SQL server is a pre-requisite (its actually SQL Edge ATM though that is being deprecated):

https://learn.microsoft.com/en-us/azure/service-bus-messaging/test-locally-with-service-bus-emulator?tabs=docker-linux-container#run-the-emulator

Deprecation Notice: https://learn.microsoft.com/en-us/lifecycle/end-of-support/end-of-support-2025

Also based on the following document do we want 2 SQL instance running in the same env?

https://learn.microsoft.com/en-us/dotnet/aspire/database/sql-server-integration?tabs=dotnet-cli%2Cssms

Could these be options being passed to the .RunAsEmulator() methods as they would only be required for the emulators.

Another option is to just spin up the emulators using the aspire docker constructs, though this is then moving away from some of the developer experiences in aspire.

[CSharpFiasco]

@davidfowl We have an Azure Functions project connected to multiple Event Hubs. They all work off the same storage account (Azure Functions doesn't seem to let us specify a different storage account per Event Hub anymore). This is our use case for reusing an existing storage resource, but admittedly, we can just use a single event hub emulator. However, due to the emulator's 10 event hub quota, this may not be appropriate for every team.

As an aside, this is great technology. Thank you for your role in getting it to where it is.