search

microsoft / vscode-azure-iot-edge

Azure IoT Edge for Visual Studio Code
https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-edge
Other
51 stars 36 forks source link

createOptions split into createOptions01, 02, 03... if too long #580

Open yahanda opened 3 years ago

yahanda commented 3 years ago

When using a deployment manifest file generated by VS code extension for IoT Edge, the following error occurred in IoT Central. https://docs.microsoft.com/en-us/answers/questions/396477/iot-central-not-upload-iot-edge-deployment-manifes.html

This is because the deployment manifest includes createOption01 when generating in VS code.

In VS Code, when right clicking a deployment.template.json file with a long createOptions and selecting Generate IoT Edge Deployment Manifest, this will create a deployment manifest file containing CreateOptions01. I have attached the samples. deployment.template.json.txt deployment.arm64v8.json.txt

IoT Central cannot accept the JSON definition that is split into createOptions and createOptions01. Is it possible to change the specifications of the extension so that they are not split even when the createOptions string is too long?

Thanks, Yasuhiro

marianan commented 3 years ago

thank you @yahanda for reporting this issue, we have added it to our backlog for investigation.

iconics-pavels commented 2 years ago

Hi, we encountered the same issue recently. I would like to know if You are going to change the client implementation, so the sections will be merged or if we should handle it in our code. If you are going to change, what's the time frame? Btw, may it happen also for some other parts of the device twin? Is it documented somewhere? Thank you.