Fix typo in az quota command group short-summary

[Hashim Khan (Hashim1999164)]

🤖 PR Validation — ️✔️ All clear

Breaking Changes
️✔️ None

Summary

• Fix Manag to Manage in the az quota command group docstring so --help shows the correct short-summary.
• Bump the quota extension to 1.0.1 and note the change in HISTORY.rst.

Fixes Azure/azure-cli#30269

Related command

az quota --help

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 azdev required)
• My extension version conforms to the Extension version schema

For new extensions:

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

Test plan

• Confirm src/quota/azext_quota/aaz/latest/quota/__cmd_group.py docstring reads "Manage quota for Azure resource providers."
• After install of the updated extension, az quota --help short-summary no longer shows "Manag".

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

Updates the quota Azure CLI extension to correct a typo in the az quota command group short-summary shown in --help, and releases the change as a patch version.

Changes:

• Fix command group docstring typo (“Manag” → “Manage”) for az quota help output.
• Bump the quota extension version from 1.0.0 to 1.0.1.
• Add a 1.0.1 entry to HISTORY.rst documenting the fix.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
src/quota/setup.py	Bumps extension package version to 1.0.1.
src/quota/HISTORY.rst	Adds release notes entry for 1.0.1 describing the typo fix.
src/quota/azext_quota/aaz/latest/quota/__cmd_group.py	Fixes the command group short-summary typo used by az quota --help.

[Yong Zhang (yonzhan)]

quota

[Hashim Khan (Hashim1999164)]

@microsoft-github-policy-service agree

[Yabo Hu (VeryEarly)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).

[Hashim Khan (Hashim1999164)]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 10144 in repo Azure/azure-cli-extensions

[Hashim Khan (Hashim1999164)]

GitHub Actions azdev-linter and azdev-style are green on this PR. The Azure Pipelines azdev jobs still show red from an earlier run, and a later /azp run was rejected for privileges. If a maintainer can re-run the Azure Pipelines checks, that should clear the stale failures.

[Hashim Khan (Hashim1999164)]

GitHub Actions azdev-linter / azdev-style are green on this PR. The Azure Pipelines style/linter jobs still show failed from an earlier run; I do not have permission to /azp run. If a maintainer can re-trigger the pipelines, that should clear the remaining red checks.

[Yong Zhang (yonzhan)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).

[Hashim Khan (Hashim1999164)]

Looked at Azure Pipelines build 335678. The azdev linter and style jobs did not fail on quota lint or flake8. They exited because scripts/ci/azdev_linter_style.py diffs against origin/main and treated src/index.json (plus other files that landed on main after this branch) as part of the PR, then raised ModifiedFilesNotAllowedError.

GitHub Actions azdev-linter and azdev-style already pass on the quota files.

I merged current main into this branch so a two-dot diff vs main is only the quota files. I cannot retrigger Azure Pipelines from this account. If a maintainer can /azp run again, that should clear the remaining red checks.

[Hashim Khan (Hashim1999164)]

Merged the latest main so this branch is no longer behind. The earlier Azure Pipelines linter/style failures looked like they came from extra files vs origin/main (including src/index.json), not from the quota typo itself. GitHub Actions azdev-linter and azdev-style already passed.

Could a maintainer run /azp run when convenient so those pipeline checks refresh?

[Yong Zhang (yonzhan)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).

[x-engineering-agent]

Live test skipped

⏭️ Skipping the live test for this revision because no new test file was added (tests/**/test_*.py).

The live-test pipeline runs only the test files a PR changes, so there is nothing to execute for this commit. This is informational — a regression test is encouraged where it makes sense, but not required. If a test file is added in a later commit, the live test will run automatically.

[x-engineering-agent]

All checks and live tests passed. Nice work! ✅