dapr / dapr/components-contrib
Support Azure Service Bus metadata handling in bindings component
- Dominant language
- Go
- Stars
- 602
- Forks
- 580
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
## Describe the feature
Per the implementation of #1071 it looks like the Azure Service Bus (ASB) queues bindings component should also be improved to support all [ASB message properties](https://docs.microsoft.com/en-us/rest/api/servicebus/message-headers-and-properties#message-headers). From the code it looks like only MessageID and CorrelationID are explicitly handled on Invoke, and Label is additionally handled on Read.
## Release Note
RELEASE NOTE: **ADD** Comprehensive Azure Service Bus message handling to Azure Service Bus Queues bindings.
Contributor guide
Research direction
Read the implementation referenced by issue #1071, then inspect the Azure Service Bus queues binding paths for Invoke and Read, where MessageID, CorrelationID, and Label are currently mentioned. Compare those paths with the linked Azure Service Bus message headers and properties reference; done means comprehensive message metadata handling is covered for the binding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100