-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Updating Compute to use Track1 2025-04-01 SDK #28578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the Azure Compute Management SDK to use the newer Track1 2025-04-01 API version, bringing enhanced capabilities and new features to Azure PowerShell's Compute module.
Key changes include:
- Version bump from 2024-11-01 to 2025-04-01 API
- New ScaleOut operation for Virtual Machine Scale Sets with zone-specific scaling
- Block capacity reservation enhancements with scheduling profiles and reservation types
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- please delete local swagger
- please merge swagger PR and check in the corresponding commit in
src/Compute/Compute.Management.Sdk/README.md
Hi @VeryEarly
This PR is to generate track1 SDK that Compute Powershell uses. |
We do not accept SDK generated by local swagger. |
Hi @VeryEarly I made the changes you suggested but ran into a lot of issues that were previously mentioned in this old PR Please help us merge this so we can deliver some Ignite features dependent on this SDK update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Description
This PR updates the Compute.Management.SDK to use latest API version 2025-04-01. This will allow compute cmdlets to use the latest SDK changes.
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.