Skip to content

Releases: Azure/iotedgedev

v0.82.0-container

11 Sep 08:00
6358655
Compare
Choose a tag to compare

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

v0.82.0

28 Aug 09:33
Compare
Choose a tag to compare

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

Breaking change for "build" command. It no longer pushes by default.

22 Mar 15:17
Compare
Choose a tag to compare

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

v0.62.0

11 Feb 07:43
Compare
Choose a tag to compare
v0.62.0 Pre-release
Pre-release

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.