Regenerate Compute SDK with latest API versions

[Haider Agha (haagha)]

Description

Regenerated the Compute management SDK from the latest published Compute API specifications used by Azure PowerShell.

• Updated the REST API specs pin to f033bb63819c74607f4086c49ae7b07a22c35f78 ([ComputeRP] New apiVersion 2026-04-01 (#42319)).
• Updated ComputeRP to 2026-04-01.
• Retained DiskRP 2026-03-02, GalleryRP 2025-12-03, and SKU 2021-07-01.
• Added generated VM and VMSS diagnostic run-command operations.
• Added generated VMSS availability-zone migration, capacity reservation, disk metadata, processor mode, extension feature metadata, gallery-sharing, and snapshot immutability SDK surfaces from these specifications.
• Updated the Az.Compute changelog with the API-version rollup.

Validation:

• Regenerated twice with the CI AutoRest toolchain and verified all 940 generated files were byte-for-byte deterministic.
• Verified the generated worktree matched the staged baseline after regeneration.
• Built Compute.Management.Sdk.csproj successfully with 0 warnings and 0 errors.
• Built src/Compute/Compute.sln successfully with 0 warnings and 0 errors.
• Verified 206 generated ComputeRP request assignments use 2026-04-01 and none remain on 2026-03-01.

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.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[ZelinWang (wangzelin007)]

/azp run

[azure-pipelines]

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

[ZelinWang (wangzelin007)]

Haider Agha (@haagha)

• Please fix the CI failures.
• Could you please add a release note for this change under Upcoming Release in src/Compute/Compute/ChangeLog.md?
  For example: https://github.com/Azure/azure-powershell/pull/29485/changes#diff-374a504f2cbf1ada502308c7713382fe2321b5a80ae5b23270a8868ded61ea18R22

[Haider Agha (haagha)]

ZelinWang (@wangzelin007) Addressed both items:

• Rebased the branch onto the latest main.
• Regenerated the Compute SDK with the CI AutoRest toolchain (@autorest/core 3.10.9, @autorest/powershell 4.0.754, and @autorest/modelerfour 4.26.2). The previous Analyze failure was caused by three generated files not matching AutoRest's exact emitted whitespace; the committed generated output now reproduces cleanly across all 911 files.
• Added the requested Upcoming Release entry in src/Compute/Compute/ChangeLog.md for DiskRP 2026-03-02 and GalleryRP 2025-12-03.
• Rebuilt src/Compute/Compute.sln: 0 warnings, 0 errors.

The corrected branch has been pushed and CI is rerunning.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 61 changed files in this pull request and generated no new comments.

Suppressed comments (1)

src/Compute/Compute/ChangeLog.md:23

• The changelog entry uses internal spec terms (DiskRP/GalleryRP) that are unlikely to be meaningful to Az.Compute users. In ChangeLog.md entries, prefer user-facing resource names (for example, managed disks / Azure Compute Gallery) and keep the wording understandable without repository-specific acronyms.

[Haider Agha (haagha)]

/azp run

[azure-pipelines]

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

[Copilot]

Pull request overview

Copilot reviewed 2 out of 179 changed files in this pull request and generated no new comments.

Suppressed comments (3)

src/Compute/Compute.Management.Sdk/README.md:34

• PR description says ComputeRP was retained at API version 2026-03-01, but this README uses the 2026-04-01/ComputeRP.json swagger. Please reconcile the PR description vs the actual AutoRest inputs (either update the description or adjust the input-file list).
  src/Compute/Compute.Management.Sdk/README.md:28
• PR description says the REST API specs pin was updated to e2ced4a78ac206eb160fa8bd070c51f5d8de0373, but this README pins commit: f033bb63819c74607f4086c49ae7b07a22c35f78. Please align the PR description and this file so they refer to the same specs commit.
  src/Compute/Compute/ChangeLog.md:23
• PR description says ComputeRP was retained at API version 2026-03-01, but the changelog entry states ComputeRP-related cmdlets now use 2026-04-01. Please confirm which ComputeRP API version is actually intended and update either the PR description or this entry accordingly.

[Haider Agha (haagha)]

/azp run

[azure-pipelines]

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