1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
Hello,
Unfortunately, IoT job for thing group deployment will not trigger again if that deployment revision for same thing name is executed before. To trigger an thing group deployment on a re-provisioned device, you will need to either 1) revise the deployment or 2) use a different thing name.
If you have a use case in which you need to re-provision devices at scale but unable to revise the deployment, we would love to hear more about it and see what we can do to improve the experience.
con risposta 2 anni fa
Thank you for your answer.
As for a use case, think of an event organiser that would have to reset its devices for every event. I am aware that there would be ways around that.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Is the deployment associated with the fleet provisioning group using any variables or substitutions in the deployment document?
Yes indeed, fleet provisioning with the thing name using variable substitution.