Releases: Azure/iotedgedev
Releases · Azure/iotedgedev
v2.1.2
Changed
- Fix error when install on Azure Pipelines agent
v2.1.1
v2.1.0
Added
- Validate schema of deployment template and generated deployment manifest in
genconfig
command
Changed
- Show progress info for docker commands
v2.0.2
Changed
- Fix errors caused by latest lark-parser release.
v2.0.1
v2.0.0
v1.3.0
Added
- Add module twin support for simulator
v1.2.0
v1.1.0
Added
- Support parsing
createOptions
in JSON dictionary format - Support multi-platform deployment manifest template, where modules' image placeholders are platform neutral (
${MODULE.filtermodule}
vs.${MODULES.filtermodule.amd64}
). You can specify the platforms to build using the--platform
parameter. By default, we provide "arm32v7", "amd64" and "windows-amd64" as the platform set since these are Azure IoT Edge supporting platforms today - Add deployment.debug.template.json when creating new solutions. This template refers to the debug flavour image of the modules and has debug
createOptions
populated automatically. You can specify the deployment manifest template to build using the--file
parameter
Changed
- Default to JSON dictionary format for newly created modules'
createOptions
- Show more clear message when failing to connect to Docker daemon
v1.0.0
Added
- Support adding Java modules
- Support adding C modules
- Add OpenJDK and Maven to IoT Edge Dev Tool Container
- Add launch.json file for Python modules
- Add
registryCredentials
to deployment manifest template
Changed
- Update .NET Core SDK in IoT Edge Dev Tool Container to version 2.1
- Improve Docker build and push command output to show more information
- Retry subscription prompt when multiple results are found
- Update launch.json file for C# modules to support .NET Core 2.1
- Fix misleading output when error deploying
- Fix error starting local registry with custom ports