[ComputeRP] New apiVersion 2026-04-01#42319
Open
haagha wants to merge 25 commits into
Open
Conversation
Next Steps to MergeNext steps that must be taken to merge this PR:
Comment generated by summarize-checks workflow run. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
Comment generated by After APIView workflow run. |
* Swagger changes for SpotPlus * Update docs * update doc * Address comments and add docs to previous properties * fix indentation * remove documentation as it is breaking cross version checks. * Revert "remove documentation as it is breaking cross version checks." This reverts commit eb18f36. * Add missing version values * Fix Go SDK generation errors * fix: suppress TCGC API version heuristic for networkApiVersion and ResourceSku.apiVersions Add @@apiversion(false) decorators to fields incorrectly detected as service API version parameters by TCGC's name-based heuristic: - VirtualMachineScaleSetNetworkProfile.networkApiVersion - VirtualMachineScaleSetUpdateNetworkProfile.networkApiVersion - NetworkProfile.networkApiVersion (all refer to Microsoft.Network API version) - ResourceSku.apiVersions (list of SKU-supported versions, not service version) This fixes Go emitter InternalError during SDK generation: unexpected constant client side default 2026-04-01 for field NetworkAPIVersion unexpected client side default kind slice for field APIVersions Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add 2026-04-01 examples for VirtualMachineScaleSetLifeCycleHookEvents operations Co-Authored-By: Copilot <223556219+Copilot@users.noreply.github.com> * Fix avocado MULTIPLE_API_VERSION: set default tag to package-2026-04-01-only Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Revert "Fix avocado MULTIPLE_API_VERSION: set default tag to package-2026-04-01-only" This reverts commit 5e41a89. * Address comments Co-Authored-By: Copilot <223556219+Copilot@users.noreply.github.com> * Update doc to generic text Co-Authored-By: Copilot <223556219+Copilot@users.noreply.github.com> * add type Co-Authored-By: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Sahil Arora <arorasahil@microsoft.com> Co-authored-by: Haider Agha <64601174+haagha@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…tween major, minor, and hotpatch coverage (#42855) * Updates documentation for the typespec parameter
* processormode support * add VMSS examples and address review comments * update description * update PR * merge validation updates
1 task
… (2026-04-01) (#42856) * Add extension metadata properties to VirtualMachineExtensionImage API (2026-04-01) Add new read-only properties to VirtualMachineExtensionImageProperties: - releaseNotes (string) - releaseCategory (ReleaseCategory union) - urgencyLevel (UrgencyLevel union) - runProfile (RunProfile union) - extensionFeatureMetadata (ExtensionFeatureMetadata model) Add $expand query parameter to listVersions operation to support returning properties including releaseCategory, urgencyLevel, and runProfile when expanded. All new types and properties are versioned with @added(Versions.v2026_04_01). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Address PR review feedback for VirtualMachineExtensionImage API - Convert \ parameter from plain string to ListVersionsExpandOptions union (extensible enum) - Remove premature 'properties/deprecationStatus' expand value - Fix ExtensionFeatureMetadata doc string for accuracy - Split ListVersions examples: MaximumSet shows default response, new WithExpandProperties example shows \=properties response - Remove releaseNotes and extensionFeatureMetadata from LIST examples (not yet rolled out) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Regenerate ComputeRP.json swagger from TypeSpec compilation Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Address @ravimeda review feedback: make key required, update @Identifiers, improve $expand description - Make 'key' required in ExtensionFeatureTag model - Update @Identifiers(#[]) to @Identifiers(#["key"]) on extensionFeatureTags - Update $expand parameter description with allowed values and effect - Regenerate 2026-04-01 ComputeRP.json swagger - Keep @added(Versions.v2026_04_01) decorators (required to prevent property leakage into older API versions) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Haider Agha <64601174+haagha@users.noreply.github.com> Co-authored-by: Audrey Toney <audreytoney@microsoft.com>
…43752) * Typespec changes - add new property to IPTag * Address comments
* Add VMSS migrateVMAvailabilityZone operation for 2026-04-01 (TypeSpec) Authors the VMSS migrateVMAvailabilityZone POST action in TypeSpec for api-version 2026-04-01. The operation is already implemented in CRP but had no public REST API spec. instanceIds is required; targetZone is optional; resourceOptions is not exposed (server defaults to Preserve). Includes generated ComputeRP.json and example. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix migrateVMAvailabilityZone example body key to match generated 'body' parameter The generated swagger body parameter is named 'body', but the example wrapped the payload under 'parameters'. oav example validation maps example keys to parameter names, so the required body was seen as missing. Renamed the inner key to 'body' in both source and generated example copies. oav validate-example now passes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix LintDiff PostResponseCodes for VMSS migrateVMAvailabilityZone Change the migrate operation to emit 202+204+default (no-content LRO POST) instead of 200(no schema)+202, satisfying the Swagger LintDiff PostResponseCodes rule. Update the example response accordingly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix: suppress arm-post-operation-response-codes for migrateVMAvailabilityZone 202+204 is the accurate contract for this no-body LRO POST per LintDiff PostResponseCodes requirements. Suppress TypeSpec ARM linter warning which only allows 202+200 for POST LRO operations. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Post-merge fixes for migrateVMAvailabilityZone (compute-2026-04-01) - Add @tag(VirtualMachineScaleSets) for SDK operation-group consistency with sibling ops - Reformat @@doc augment per v1.12 TypeSpec formatter (multi-line) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Refine migrateVMAvailabilityZone description wording Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Introduced examples for creating, updating, deleting, and retrieving Interconnect Blocks. - Added examples for listing Interconnect Blocks by resource group and subscription. - Included instance view retrieval example for Interconnect Blocks. - Updated ComputeRP.json to reference new examples and provide clearer descriptions for script handler versions and VM priorities.
Contributor
|
Please fix Required CI checks first. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.
Getting help
Purpose of this PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.