[IoT] Adds IoT Extension v0.30.0b1 to the index

[c-ryan-k]

Notes for this preview release can be found here:
https://github.com/Azure/azure-iot-cli-extension/releases/tag/v0.30.0b1

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @c-ryan-k,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[github-actions]

• For more info about extension versioning, please refer to Extension version schema

[Copilot]

Pull Request Overview

This PR adds IoT Extension version 0.30.0b1 (beta) to the Azure CLI extensions index, along with associated linter exclusions for various IoT commands.

• Adds new extension version 0.30.0b1 with updated dependencies and Python 3.9-3.13 support
• Updates minimum Azure CLI core version requirement to 2.67.0
• Adds linter exclusions for multiple IoT commands to suppress specific linting rules

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/index.json	Adds metadata entry for azure-iot v0.30.0b1 including dependencies, classifiers, and download information
linter_exclusions.yml	Adds linter rule exclusions for various IoT commands including DPS, hub, and ADR namespace policy operations

[Copilot]

The run_requires list contains duplicate dependency specifications with different formatting styles (e.g., 'azure-core (<2.0.0,>=1.24.0)' with spaces and 'azure-core<2.0.0,>=1.24.0' without spaces). Each dependency appears twice in the list, which is redundant and could cause confusion. Consider removing the duplicate entries and keeping only one consistent format per dependency.

[necusjz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[zhoxing-ms]

Traceback (most recent call last):
File "/mnt/vss/_work/1/s/src/containerapp/setup.py", line 13, in
from azext_containerapp._utils import get_pack_exec_path
File "/mnt/vss/_work/1/s/src/containerapp/azext_containerapp/init.py", line 7, in
from azure.cli.core import AzCommandsLoader
ModuleNotFoundError: No module named 'azure.cli.core'

Please resolve this CI issue

[c-ryan-k]

Traceback (most recent call last):
File "/mnt/vss/_work/1/s/src/containerapp/setup.py", line 13, in
from azext_containerapp._utils import get_pack_exec_path
File "/mnt/vss/_work/1/s/src/containerapp/azext_containerapp/init.py", line 7, in
from azure.cli.core import AzCommandsLoader
ModuleNotFoundError: No module named 'azure.cli.core'

Please resolve this CI issue

@zhoxing-ms I'm not sure how to fix an issue in containerapp?

This looks like a generic pipeline failure that's unrelated to our extension, and I can't run CI anyway until someone from your team kicks it off. I would suggest just running it again, it looks like there were several similar pipeline failures around that time.

[necusjz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).