Generate Compute SDK using autorest.powershell#28976
Conversation
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
src/Compute/Compute.Management.Sdk/Customizations/VirtualMachineScaleSetVMsOperations.cs
Show resolved
Hide resolved
|
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. |
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
I believe no Changelog edits are needed because we are just updating the SDK generation method and not adding anything new, but let me know if I misunderstood |
|
@audreyttt Change log is required because a new package should be released. Additionally, I noticed the casing of some property names has been changed. Can you please confirm if these properties are part of the output objects? If so, it will cause potential breaking changes to the customers if they reference the classes directly using C# code. The recommended way is to use directives to rename the properties. |
|
All tests are passing in Playback mode post-migration and a few tests per critical resource group (VM, VMSS, Gallery, Disk) were run in Record mode and are confirmed to be working post-migration as well. |
Description
Uses autorest powershell to generate SDK and replace the deprecated Track 1 SDK
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.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.