Code sample for identity translation pattern.
If the development team is busy, some guidance on how does the module(who understand native protocols and gives device identity) receive the connection string will be helpful. Hard coding connection strings is not is not an option.
Kiran Pradeep
shared this idea
10 comments
-
This is still a very high priority for our team and we're trying to align all of our dependencies to deliver this. Progress has been far slower than desired as we've improved product stability and deliver fundamental features like device update, observability (the ability to collect logs and metrics from an IoT Edge device), and improved certificate management.
-
Gancho, Dmitry
commented
@Chipalo, any update on the work-in-progress? It's been almost 2 years since your post
-
António Sérgio Azevedo
commented
Adding two other samples that may help workaround this request while it's being implemented: https://github.com/gtrifonov/iotc-edge-device-bridge
https://github.com/Azure/iotedge-lorawan-starterkitThank you!
-
Pavan Mahadev Pawar
commented
Is there any update on this?
-
Lukas Terhall
commented
It's been about a year and a half now - is this item still "high on your list?" A code example of identity translation would be much appreciated.
-
Serge RICARDO - Kirrk
commented
Hi Chipalo, any news about this subject ?
Is it worthy to spend time trying to do Identity translation (thousands of downstream devices) or, for the moment, is it better to consider Protocol translation pattern ?
Thank you in advance for your feedback. -
Euler, Jens
commented
Hi Chipalo, can you elaborate how one can send the connection strings in the twin? I thought the device would need a connection string to access the twin. Any link to a python sample maybe? Thank you very much
-
Scott Kaul
commented
Is there an example of either using connection strings in the twin of the module or an example of identity translation available yet? Either would be really helpful to me right now.
-
Anonymous
commented
a year has gone, wonder if work in progress is progressing at all
-
A temporary work around is sending the connection strings in the twin of the module. The longer term approach requires integration with Device Provisioning Service. That is work in progress.
