IoT CLI Feature Release Flow (Control Plane)

This document describes the end-to-end flow for delivering new IoT Hub control plane features to Azure CLI and IoT CLI extension.

It is intended for service teams to understand:

• What needs to be provided (e.g. swagger, API version)
• When CLI teams can onboard the feature
• How release timelines align across SDK, CLI, and extension

Scope

This document focuses on:

• Control plane APIs
• GA release flow

Out of scope:

• Data plane features
• Private preview / public preview release strategies

High-Level Flow

The typical GA release flow follows this sequence:

1. Service team publishes new swagger (API version)
2. Python SDK is generated and published to PyPI
3. Azure CLI consumes the new SDK version
4. IoT CLI extension implements new functionality
5. Feature is released to customers

Independent Extension Release

The IoT CLI extension can be released independently of the Azure CLI release train.

If API version handling is implemented correctly, new functionality can be shipped:

• In parallel with CLI
• Or before CLI release

Known Challenges

• SDK generation may lag behind swagger updates
• CLI release train introduces additional delay
• Preview scenarios require custom handling
• API version compatibility must be managed carefully