iotedgedev

Changed

• Fix build errors when some projects under modules folder have no module.json [#396]

Added

• Support relative path for module placeholder in deployment.template.json

Changed

• Fix issue with 'cs' keyerror [#387]. Thanks for jporcenaluk's contribution.
• Drop support for ACTIVE_DOCKER_PLATFORMS environment variable

Added

• Add module twin support for simulator

Added

• Validate schema of deployment template and generated deployment manifest in genconfig command

Changed

• Show progress info for docker commands

Changed

• 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]

Changed

• Fix error when install on Azure Pipelines agent

Changed

• Fix genconfig does not fail when schema validation failed. [#424]

Changed

• 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]

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

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

This release only contains various bug fixes for the Dockerfiles of IoT Edge Dev Container.

Added

• 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

Changed

• 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

Removed

• Support for iotedgectl and public preview runtime images

With this release, the build command will no longer push to container registry by default.

If you want to always push, then use either:

iotedgedev build --push

or

iotedgedev push

If you want to push, without building, then use this:

iotedgedev push --no-build

Breaking Changes

1. "project" command renamed to "solution"
2. Config files are in the root now and are renamed to runtime.template.json and deployment.template.json
3. Dockerfiles moved to root of project instead of /Docker/arch folders.
4. Greatly simplified .env file and added comments. The only required settings now are IOTHUB_CONNECTION_STRING and DEVICE_CONNECTION_STRING
5. Added module.json file to module root - and this file is now required for all modules. It maps arch to Dockerfile locations and specifies version number. Sample module.json file can be found here.
6. ACTIVE_DOCKER_DIRS renamed to ACTIVE_DOCKER_ARCH and this filters on module.json/platforms entries instead of folders.

New Commands

1. Added iothub --monitor-events command to easily view messages flow from device to iothub.
2. Added azure --setup command to assist in creating/selecting IoT Hub and Device and outputting connection strings to .env file.

Other Changes

1. Config files expanded to .config directory instead of /build/config
2. Modules are built in place and are not copied to /build folder
3. Build folder completely removed. Not needed anymore.
4. Added support for DOTENV_FILE environment variable override, so you can specify a different .env file to load. Helpful for CI/CD scenarios.
5. Container images now have a version tag that is pulled from module.json file
6. CONTAINER_TAG is set to "" by default instead of "latest". CONTAINER_TAG isn't really needed anymore since we now have version.
7. Created an Azure IoT Edge Dev Tool container: https://github.com/jonbgallant/azure-iot-edge-dev-tool#iot-edge-dev-tool-container
8. Renamed filter-module to filtermodule due to a .NET core template bug that doesn't handle "-" well.