Operational models for Azure IoT Hub #382
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nger need IIotHubEvent
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds models that help work with Azure IoT Hub from an operational perspective. Alongside telemetry, other events are received. These include
twinChangeEvents,lifecycleEvents, anddeviceConnectionStateEvents. These are useful in production.This PR introduces models that abstract much of the common logic in getting these out of received events and reacting accordingly. This is enabled through a custom type
IotHubEvent<TDeviceTelemetry, TDeviceTwinChange, TDeviceLifecycle>and the shorterIotHubEvent<TDeviceTelemetry>together with a custom serializer.The
AzureIotHubsamples has been updated to show the recommended usage.