Ability to specify transport type for event hubs in the new 2.0.0 package.

[talhanaveedcoop]

In version 1.5.4, we used EventHubsConnectionStringBuilder from Microsoft.Azure.EventHubs, which had a TransportType property that allowed us to specify AMQP WebSockets. The new Azure.Messaging.EventHubs package's EventHubsConnectionStringProperties doesn’t have this property, and it defaults to AMQP.

Our company's network blocks AMQP ports, so I need to use AMQP WebSockets to run the code locally. Could you add an option to specify TransportType in Netherite? This would help in environments where AMQP is restricted.

It seems like a simple and useful addition.

Thank you!

[sebastianburckhardt]

Could you add an option to specify TransportType in Netherite?

Adding a configuration setting for a connection is not extremely straightforward since in Azure Functions, connections are usually configured via an indirection (using a connection name, which is then resolved to one or more parameters). I suppose it is possible. Our best bet may be to add this at the same time as support for managed identity since that already requires the ability to configure multiple parameters for a connection.