microsoft / microsoft/durabletask-netherite
Ability to specify transport type for event hubs in the new 2.0.0 package.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 239
- Forks
- 37
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
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!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate Netherite's Event Hubs configuration and the code that creates Azure.Messaging.EventHubs clients; the issue identifies EventHubsConnectionStringProperties and the former EventHubsConnectionStringBuilder.TransportType as relevant API points. Determine how an AMQP WebSockets option should be exposed, then verify that restricted AMQP environments can select it without changing the default transport.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100