IoT Central - not upload IoT Edge deployment manifest if contains createOption01

Yasuhiro Handa 26 Reputation points Microsoft Employee

When creating a Device Template for IoT Edge, the following error has been occurred if specifying deployment manifest with createOption01.


Previously, IoT Central could accept the JSON definition that was split into createOption and createOption01 if the createOption string was long, but the specification seems to have changed.
After connecting createOption and createOption01, the error was resolved, but is this an IoT Central specification?



Azure IoT Central
Azure IoT Central
An Azure hosted internet of things (IoT) application platform.
331 questions
0 comments No comments
{count} votes

Accepted answer
  1. António Sérgio Azevedo 7,661 Reputation points Microsoft Employee

    Hello @YasuhiroHanda-1129 ,

    createOptions parameter is a specification of Azure IoT Edge Device Modules and belongs to the deployment manifest - it enables you to configure the module containers at runtime.

    Therefore, Azure IoT Central should comply with the definition in Azure IoT Edge documentation like described here:

    In that doc I can't see a mention to "split" to createOptions01, 02, 03... JSON object if too long, therefore I would suggest you continue using only one JSON Object createOptions in your Device Template for IoT Edge.

    Hope I could help. Thank you!


    • Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.
    • Want a reminder to come back and check responses? Here is how to subscribe to a notification.

0 additional answers

Sort by: Most helpful