Our deepstream-derived applications will be deployed as an Azure IoT Edge module (container). I am evaluating the nvmsgbroker and nvmsgconv gst plugins as the means by which our applications can communicate back to our web portal via Azure IoT. I’m reading the details in the section entitled " Connection Details for the Module Client Adapter" at this link: Gst-nvmsgbroker — DeepStream 5.1 Release documentation
If the documentation matches the implementation then I am concerned about how libnvds_azure_edge_proto has been implemented. Specifically, this looks incorrect:
“Leave the connection string empty, since the Azure IoT Edge library automatically fetches the connection string from the file
If your application is running as an Edge module (container) then you will not have access to this file. Furthermore, it wouldn’t work if you were using the Device Provisioning Service vs pre-provisioned devices with connection strings. In either scenario the protocol adapter should have received it’s connection via this call:
Since this source seems to not be published (someone else has already posted about that - no reason this should be made public) then I’m unable to confirm the implementation. Please advise. As an alternative I could simply write my own gst message broker, but I wanted to give NVIDIA’s intended implementation due consideration.