Ability to use Wolverine in connection with Azure Service Bus Emulator

[mvein]

Is your feature request related to a problem? Please describe.
I was trying to use Wolverine together with Azure Service Bus Emulator, but since ASBE does not support SSL, it is not possible to connect with Wolverine as this one listens on 443 port only (or it is not obvious to change the default behavior).

[15:37:05 INF] Initializing the Wolverine AzureServiceBusTransport
[15:37:27 ERR] Failed to start the Wolverine messaging
System.AggregateException: Retry failed after 4 tries. Retry settings can be adjusted in ClientOptions.Retry or by configuring a custom retry policy in ClientOptions.RetryPolicy. (No connection could be made because the target machine actively refused it. (localhost:443)) (No connection could be made because the target machine actively refused it. (localhost:443)) (No connection could be made because the target machine actively refused it. (localhost:443)) (No connection could be made because the target machine actively refused it. (localhost:443))

Describe the solution you'd like
An ability to run Wolverine with ASBE on any port of choose.

Additional context
Configuration used:

.UseWolverine(options =>
{
    var connectionString = builder
        .Configuration
        .GetConnectionString("AzureServiceBus");

    // Connect to the broker in the simplest possible way
    options.UseAzureServiceBus(connectionString!)
    .AutoProvision();

    options.ListenToAzureServiceBusQueue("queue.1")

        // Customize how many messages to retrieve at one time
        .MaximumMessagesToReceive(100)

        // Customize how long the listener will wait for more messages before
        // processing a batch
        .MaximumWaitTime(3.Seconds())

        // Add a circuit breaker for systematic failures
        .CircuitBreaker()

        // And all the normal Wolverine options you'd expect
        .BufferedInMemory();

    // Auto-discover message handlers
    options.Discovery.IncludeAssembly(typeof(Program).Assembly);
});

[jeremydmiller]

@mvein When you configure the Azure Service Bus transport, there's an optional, 2nd argument in UseAzureServiceBus() that let's you configure the ServiceBusClientOptions, surely there's something with that to allow this? There's also an UseDevelopmentEmulator=true; option for the connection string. I'm willing to be wrong, but I can't imagine we really need code changes to allow for this.

Happy to take a pull request either for real changes or for documentation updates just showing folks how to use it

[mattjedge]

I've been struggling with the same problem this last week. I'm setting up a new minimal API project using Aspire and Wolverine. It took me a couple of days of tinkering before considering it was an issue between wolverine and the emulator specifically.

I hooked the project up to a dev SB to check and it all worked as expected. However, upon swapping config back to using the emulator, that's all working fine now too. No configuration changes on the emulator itself before vs after swapping it for the real thing. 🤷

I'm not sure how helpful an anecdote this is, but certainly an interesting bit of behaviour. I'll report back if I discover the cause / if it reverts back to throwing exceptions.