Federico Mariani created CAMEL-26809:
----------------------------------------
Summary: camel-azure-iothub: service-side operations (send C2D
message, invoke direct method, read and update device twins, query twins)
Key: CAMEL-26809
URL: https://issues.apache.org/jira/browse/CAMEL-26809
Project: Camel
Issue Type: New Feature
Components: camel-azure
Reporter: Federico Mariani
CAMEL-22624 asked for a component wrapping the IoT Hub *service* SDK. [PR
#29489|https://github.com/apache/camel/pull/29489] implements the *device* side
only (telemetry and reported properties sent as the device). The backend
operations are still missing:
* send a cloud-to-device message: {{MessagingClient}}
* invoke a direct method on a device: {{DirectMethodsClient}}
* read a device twin, update desired properties and tags: {{TwinClient}}
* query device twins: {{QueryClient}}
SDK: {{com.microsoft.azure.sdk.iot:iot-service-client}} (2.1.11, source in
Azure/azure-iot-service-sdk-java). Authentication differs from the device side:
a shared access policy connection string or a {{TokenCredential}} (Microsoft
Entra ID).
h3. To decide first
Where these operations live: in camel-azure-iothub behind an {{operation}}
option, as other Azure components do, or under a separate scheme. The URI in PR
#29489, {{azure-iothub:deviceId}} with a device connection string, belongs to
the device side. Ideally this is settled before the component ships in 4.24, so
the URI does not change after a release.
h3. Later
Once sending C2D messages is supported: consumers for C2D delivery feedback
({{MessageFeedbackProcessorClient}}) and for file upload notifications
({{FileUploadNotificationProcessorClient}}).
h3. Out of scope
Reading device-to-cloud telemetry. The service SDK has no API for it; the
camel-azure-eventhubs consumer already reads it from the IoT Hub built-in Event
Hubs-compatible endpoint.
_Claude Code on behalf of Croway_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
