You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As Developer,
Would be great to be able to have a Dev Service in Quarkus that allows me to use Azure IoT Hub without requiring any internet connection for my local environment.
As you know, Azure IoT Hub supports two types of connection:
iot-service-client ( register and send messages/events from cloud to device)
iot-device-client ( receive and send messages/events from device to Cloud)
I would like to be able to make two operations:
Register Devices
Send messages/events to a registered device that was created using the operation above or it was a pre-populated device via application.properties
When sending messages to a pre-populated device it would be great to define a few properties:
First, this would require Azure IoT clients to be supported on Quarkus through dedicated extensions.
Second, Quarkus dev services typically (but not necessarily) use Testcontainers for mocking the backend. Do you know whether there is any Testcontainer available for Azure IoT Hub? Azurite does not seem to support it.
@agoncal does Microsoft have any strategy for delivering Testcontainers for the individual Azure services?
As Developer,
Would be great to be able to have a Dev Service in Quarkus that allows me to use Azure IoT Hub without requiring any internet connection for my local environment.
As you know, Azure IoT Hub supports two types of connection:
I would like to be able to make two operations:
When sending messages to a pre-populated device it would be great to define a few properties:
quarkus.azure.iothub.device."quarkus-device1".status=enable/disable
quarkus.azure.iothub.device."quarkus-device1".message.acknowledgment=true/false
quarkus.azure.iothub.device."quarkus-device1".message.acknowledgment.delay=5000 (ms)
Documentation:
https://learn.microsoft.com/en-us/java/api/overview/azure/iot?view=azure-java-stable
The text was updated successfully, but these errors were encountered: