Allow to pass CustomEndpointAddress to ServiceBusClientOptions

[scrocquesel-ml150]

Description

We are using a docker container to emulate Azure Service Bus, while it works like a charm with Azure SDK Client, it seems Azure Function do not use the same client factory as Microsoft.Extensions.Azure.

In other words, we want the client to be create with

    var sbClient = new ServiceBusClient(configSection["fullyQualifiedNamespace"],
            new ServiceBusClientOptions()
            {
                TransportType = configSection["transportType"],
                CustomEndpointAddress = configSection["customEndpointAddress"],
            });

The factory in Microsoft.Extensions.Azure make use of reflection to bind the config section to the ServiceBusClientOptions.
Something similar is done in the webjobs extension but it misses the CustomEndpointAddress property.

[jviau]

In dotnet isolated the service bus client used is in an entirely different process, so configuration via code won't be possible here. @JoshLove-msft is it possible to read this value from IConfiguration in the WebJobs extension? Or is it already supported?

[JoshLove-msft]

Yes, this is already supported in the WebJobs extension.

[jviau]

Yes, this is already supported in the WebJobs extension.

@JoshLove-msft is it supported via configuration? Or is it code only?

[JoshLove-msft]

My mistake - the CustomEndpointAddress is not available in the webjobs extension via config or code. It would need to be added into the ServiceBusOptions type, and then consumed in the builder extension. Is the ask here to support it in the WebJobs extension?

[scrocquesel-ml150]

My mistake - the CustomEndpointAddress is not available in the webjobs extension via config or code. It would need to be added into the ServiceBusOptions type, and then consumed in the builder extension. Is the ask here to support it in the WebJobs extension?

Yes, my request is to be able to pass the CustomEndpointAddress with the connection configuration section to the dotnet isolated service bus trigger. Does the webJobs extension is for both isolated and inprocess ?

[jviau]

Yes, the ask would be to support this in the WebJobs extension. This will cover both in-proc and isolated.

@scrocquesel-ml150 when supported, you will need to set it via host.json or an app setting / env variable. This is because in dotnet isolated, the host process loads the WebJobs versions of the extensions, and that is what performs all interactions with the actual service bus.

[JoshLove-msft]

Sounds good, I will file this in the azure-sdk-for-net repo where the code lives.