dapr / dapr/components-contrib

can pubsub.azure.servicebus.topics control connection type?

Open
#3,038 5 comments 0 reactions 0 assignees View on GitHub
help wanted kind/enhancement
Dominant language
Go
Stars
602
Forks
580
Avg merge
4d 9h
Merged PRs (30d)
6

Description

Scanning the code base i do not find any way to specify that the servicebus client be created with the AmpqWebSockets transport type.

I dont think that this is possible via metadata for the component, but wanted to double-check.

We are not able to connect for pub or sub via Dapr from an on-prem component due to firewall restrictions. But I can code up my own subscriber and make this connection outside of Dapr by specifying the client options transport type as AmpqWebSockets.

Obviously I would have preferred having the ability to control this with pubsub component spec, but possibly there are design reasons that this is not the case. If not, I can re-raise this as a feature request.

Contributor guide

Open the contributing guide

Research direction

Start by scanning the pubsub.azure.servicebus component and its metadata handling for the client transport configuration. Determine whether AmpqWebSockets can be selected through the component specification; done means establishing the supported behavior and, if it is not supported, defining the feature scope before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, go
Domain
cloud, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.