Open ssnseawolf opened 1 week ago
Thanks for the suggestion! The only concern is the emulator is only for serverless -- for this we could check if the service is added in "Serverless" mode, and let RunAsEmulator throw during runtime if it not.
@davidfowl can you check with the SignalR team to see if it's possible to create a container image for this (as opposed to using a dotnet tool)? That way it could be the same as the other patterns we already have.
@vicancy is on the SignalR service team 😄
@davidfowl can you check with the SignalR team to see if it's possible to create a container image for this (as opposed to using a dotnet tool)? That way it could be the same as the other patterns we already have.
Sure our team will work on this.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
Aspire does not have an Azure SignalR
RunAsEmulator()
method to wire up the Azure SignalR local emulator.Describe the solution you'd like
An Azure SignalR serverless local emulator is available as a
dotnet tool
as Microsoft.Azure.SignalR.Emulator.From the customer side, it seems natural for Aspire to offer a
RunAsEmulator()
method to wrap up the dotnet tool and handle the networking friction.Additional context
No response