Repository navigation
fix: Update token budget limits - Microsoft.AIInfraOptimization - #10580
Kunal Karmakar (kkarmakarMS) wants to merge 3 commits into
Conversation
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
There was a problem hiding this comment.
🟡 Changes recommended
The command tests lack regression coverage for both token fields above the old 131072 ceiling, including acceptance at the new upper boundary and rejection above it.
1 open issue
What changed in this PR
Updates argument validation for az aiinfraoptimization recommendvmsku to match the token-budget limits in the linked AAZ change.
Changes:
- Raises the maximum for both token-budget fields from 131072 to 2147483647, retaining a minimum of zero.
- Changes the help example’s model parameter count to 70 billion.
| File | Description |
|---|---|
src/aiinfraoptimization/azext_aiinfraoptimization/aaz/latest/aiinfraoptimization/_recommendvmsku.py |
Increases token argument limits and adjusts the documented example. |
Review effort: Balanced
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
ba8a94a to
dce9f73
Compare
|
Kunal Karmakar (@kkarmakarMS) Both client-side token limits increase to To addressTick each item as you address it.
Review detailsUpstream CIThe handoff reports six completed checks, five passed and zero failed. The author's checklist reports local style and extension-index checks, not expanded-range service validation. Test validation
The new scenario test replaces command execution and output with request-body construction at For Risk assessment46/100 · Medium The Medium rating is driven by public CLI behavior, dependency or supply chain, generated output.
Ask the Agent Tick a box to queue an action. Requires write access to this repository.
|
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
dce9f73 to
19674ea
Compare

🤖 PR Validation — ️✔️ All clear
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az aiinfraoptimizationAAZ PR: Azure/aaz#1165
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install azdevrequired)For new extensions:
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.jsonautomatically.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.