azure-cli-iot-ext 0.8.9

• Updated uamqp version to ~1.2.
• Simplified out-of-band dependency installation message.
• If uamqp installation fails the error is raised on stderr rather than having to use --debug.
• amqp frame traces are not shown when --debug is passed in to event monitoring.
• Fixed monitor-events not raising an exception if receiver client runs into an error.

azure-cli-iot-ext 0.8.8

• Introducing the addition of the job command set az iot hub job
  • Supersedes the vanilla Azure CLI IoT job commands. The vanilla commands are deprecated and scheduled for removal.
  • Allows the creating and scheduling of v2 Jobs for at scale device manipulation. This includes scheduleUpdateTwin and scheduleDeviceMethod.
    • Throttling limits apply
  • Show/List/Cancel command operations work against both v1 and v2 jobs providing a 'single pane' experience.

azure-cli-iot-ext 0.8.7

The following features depend on service capabilities that will be released soon.

• Support IoT Edge layered deployments.
• Support ADM module twin definitions.

The remaining features are generally available.

• Improved json schema validation error handling for edge deployments.
• Update top maximum for hub config/edge deployment list to 100.
• Breaking Change: Metric evaluation between hub configurations and edge deployments via show-metric work exactly the same.
• Breaking Change: New result format for az iot device c2d-message receive. The command now shows all properties.
• Updated IoT Central commands to allow the API for token collection to be overridden.
• az iot device c2d-message send supports sending all settable system properties per message.
• Updated uAMQP version range.
• Add user agent for MQTT & AMQP operations.
• Add QoS argument for send-d2c-message.

azure-cli-iot-ext 0.8.7rc1

• Support IoT Edge layered deployments.
• Support ADM module twin definitions.
• Improved json schema validation error handling for edge deployments.
• Update top maximum for hub config/edge deployment list to 100.
• Metric evaluation for hub configuration and edge deployment via show-metric work exactly the same.

azure-cli-iot-ext 0.8.6

• For IoTHub commands - improves json handling for arguments that require json.
  • For overloaded arguments which can be a file path or raw json, if an input file path does not exist but looks like a file (ends in a common file prefix) then the CLI will provide a warning indicating so.
  • Clearer error messages if json parsing fails. The error describes the failed argument and the file (if applicable).
• Edge deployments support metric definitions at creation time via --metrics argument (like device configurations).
• Fixes issue with az iot hub invoke-device-method preventing primitive value payloads.
• The az iot device simulate command will send default values for content-type and content-encoding. These values can be overridden.

azure-cli-iot-ext 0.8.5

• Re-adds deprecated parameter --config-id to edge related commands (resolves issue #113 )
  • Note: --deployment-id/-d are the proper parameters to use in place of config-id when using edge deployment related commands.

azure-cli-iot-ext 0.8.4

• Device simulate now supports sending arbitrary message properties (like in send-d2c-message) (issue #103)
• The preview dt monitor events command has been simplified. It works the same as vanilla iot hub monitoring but filters dt events and allows filtering by interface
• Help content improvements
• Removed long since deprecated parameter --config-id from edge related commands

azure-cli-iot-ext 0.8.3

• Removes long since deprecated command az iot hub apply-configuration
• Resolve issue #100
• Improve help content for az iot edge deployment update to explicitly show what can be updated in an existing edge deployment.
• Fix message annotation used to filter Digital Twin events in az iot dt monitor-events

azure-cli-iot-ext 0.8.2

• Resolve jsonschema load issue.

azure-cli-iot-ext 0.8.1

• PnP monitor events commands - Adds an option for filtering devices by twin query.
• PnP monitor events commands - Some existing mandatory parameters are now optional.
• Added support for iot central commands - monitor-events and device-twin show.
• Schema validation applies for creation of IoT Edge deployments or when setting modules per device.