Azure IoT Edge 1.0.1 release
Updated: August 22, 2018
The 1.0.1 update of Azure IoT Edge includes the following improvements.
Multiple bugs have been resolved in both Edge Hub and Edge Agent. (A full change list is in the release notes on GitHub.) You must manually delete the container image for each component if you're already using Azure IoT Edge and want to receive the fixes.
You can optimize Edge Hub memory usage by turning off protocol heads for any protocols not used by Edge modules in your solution. You can set the following environment variables on Edge Hub to enable/disable specific protocol heads. Note that there are two underscores in the environment variables.
- Key - “amqpSettings__enabled”, value – “true/false”
- Key - “mqttSettings__enabled”, value – “true/false”
- Key - “httpSettings__enabled”, value – “true/false”
A bug that intermittently prevented C# modules from connecting to Edge Hub when using MQTT (GitHub issues: 19, 521, 558) was resolved. This issue was in DotNetty, a dependency of the C# Client SDK. DotNetty was fixed and integrated into the C# Client SDK version 1.18.0. Users must also update their modules to use the latest version of the C# Client SDK to fully resolve the issue. The Functions module used in the Filter data with Azure functions tutorial was updated to use the new version of the C# SDK. You must manually delete the container image for this component if you're already using it and want to receive the fix.
An installation script for Windows was released. This makes the setup of IoT Edge on a Windows a more reliable process by reducing the number of steps a user takes to install the runtime. The script is included in the documentation for installing IoT Edge on Windows (Windows quickstart, Windows with Windows containers, Windows with Linux containers).
An article that explains Security Manager was added to product documentation.