All notable changes to this project since 0.82.0 will be documented in this file.
- Lock .NET Microsoft.Azure.IoT.Edge.Module version at 3.2.0
- Lock simulator version at 0.14.18
- Update docker compose
- Update simulator version
- Update azure-cli-core
- Enable
iotedgedev solution deploy
with a DPS connection string - Deprecate duplicate commands
- Fix issue with traceback error not being outputted from the
iotedgedev monitor
command - Fix issue when provisioning default IoT Hub SKUs (F1) with
iotedgedev iothub setup
- Add
iotedgedev init
an option to initialize in a new folder
- Lock simulator version at 0.14.14
- Update Wiki and dev container to reflect changes about the simulator
- Add support for python 3.8, 3.9
- Lock simulator version at 0.14.12
- Upgrade docker SDK to version 5.0.3
- Lock simulator version at 0.14.11
- Updated Python Docker package versions to newest version and enable simulator dependencies
- Add support for layered deployment manifests when building, pushing and generating
- Add support for creating deployments in IoTHub via the new command:
iotedgedev iothub deploy
- Add support for adding device tags via the new command:
iotedgedev tag
- Added support for IoT Edge Runtime version 1.2
- Enable change of edgehub and edgeagent schema versions
- Added support for config generation, build and push off of a layered deployment manifest
- Added support for IoT Edge Runtime version 1.1
- Enabled dynamic Edge runtime selection in CLI with -er flag
- Remove support for Python2. Only Python 3.6 and 3.7 are currently supported.
- Remove explicit cryptography package install to resolve dependency conflicts so tests can run
- Add local registry support for Windows
- Fix warning about ConfigParser readfp deprecation
- Fix error caused by latest bcrypt on Azure Pipelines agent
- Fix configparser error from Azure Cli Core [#426]
- Fix genconfig does not fail when schema validation failed. [#424]
- Fix error when install on Azure Pipelines agent
- Fix getconfig fails if template contains a placeholder that is not enclosed in quotes.[#414]
- Fix wrong instruction to
iotedgedev iothub setup
with extra flags.[#417] - Python 3.8 is not supported due to Azure CLI IoT extension issue [#128]
- Validate schema of deployment template and generated deployment manifest in
genconfig
command
- Show progress info for docker commands
- Fix errors caused by latest lark-parser release.
- Fix build errors when some projects under modules folder have no module.json [#396]
- Support relative path for module placeholder in deployment.template.json
- Fix issue with 'cs' keyerror [#387]. Thanks for jporcenaluk's contribution.
- Drop support for ACTIVE_DOCKER_PLATFORMS environment variable
- Add module twin support for simulator
- Update azure-cli-core to fix module import error
- Fix applicationinsights incompatible version issue [#383]
- Fix issue creating C modules when temp folder and target project folder are on different disks [#362]
- Fix issue connecting to Docker daemon with
tlsverify
enabled [#364] - Preserve tag cases when generating deployment manifests [#372]
- 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
- Default to JSON dictionary format for newly created modules'
createOptions
- Show more clear message when failing to connect to Docker daemon
- 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
- 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
- New command to add modules to solution
- Support for adding and building Node.js and Python modules
- Integration with IoT Edge Simulator provided by the iotedgehubdev CLI
- Allow specifying name and template of the default module when creating new solutions
- Support for build options in
module.json
file - Support for customized context path in
module.json
file - Support for multiple registries in
.env
file - Support for GA release of IoT Edge runtime in IoT Edge Dev Container
- Update
.vscode/launch.json
file when adding modules
- Switch to Azure CLI IoT extension (>= 0.5.1) to monitor messages for Python >= 3.5 users
- Improve experience of creating Azure resources interactively
- Breaking changes (learn how to migrate here)
- Updated command list and options
- Updated logic to determine which module images to build
- New module folder structure
- Building code in Dockerfiles instead on building code natively
- Support for
iotedgectl
and public preview runtime images
- First release on PyPI.