dapr / dapr/components-contrib
EventHub.properties are not available while subscribing to Azure IoT Hub Events
- Dominant language
- Go
- Stars
- 602
- Forks
- 580
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
## Expected Behavior
Scenario: IoT enrichment properties are supplied as EventHub.properties when sent to the Event Hub using the routing. These properties are currently not exposed while accessing Dapr.
Because of this it creates a dependency to use the SDK
## Actual Behavior
EventHub.properties are not available while subscribing to Azure IoT Hub Events
Briefly mentioned in the other issue: https://github.com/dapr/components-contrib/issues/1151
Contributor guide
Research direction
Start by reviewing the related issue 1151 and tracing the Azure IoT Hub Event Hub subscription path in the components-contrib repository. Done means that EventHub.properties supplied through IoT Hub routing are exposed when subscribing through Dapr, removing the stated need to use the SDK.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100