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
Since both deployments targets the same module only the deployment with the later creation date will be applied. In this case that would be Deployment 2.
The result is that only test2.txt is created on the device.
This means that there is now way of ensure offline devices coming online gets both deployments applied.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We have use case where we have devices that could be offline for long periods.
It seems like OSConfig CommandRunner is meant to be used for online devices, because only the last module twin configuration will be used.
Example:
Switch off the IoT Edge device.
Create 2 deployments with target condition:
from devices.modules where moduleId='osconfig'
Deployment 1:
Deployment 2:
Since both deployments targets the same module only the deployment with the later creation date will be applied. In this case that would be
Deployment 2
.The result is that only
test2.txt
is created on the device.This means that there is now way of ensure offline devices coming online gets both deployments applied.
Is there a way around this?
Beta Was this translation helpful? Give feedback.
All reactions