Add Bulkactions 2026-07-06-preview version#43925
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
Comment generated by After APIView workflow run. |
|
ARM review update for latest iteration (head: e0b058b):
Validation status checked for this changeset:
Action required:
|
2) Added suppression for record<unknown> in baseProfile and resourceOverrides of ResourceProvisionPayload
| operationId: string; | ||
|
|
||
| @doc("Unique identifier for the resource involved in the operation, for example Azure resource ID") | ||
| resourceId?: armResourceIdentifier; |
There was a problem hiding this comment.
This is an unversioned change. Is this a correction, or is this meant to be in the new version only?
There was a problem hiding this comment.
only the doc only unversioned changes are allowed in the previous versions, will update this.
| @doc("High level response from an operation on a resource") | ||
| model ResourceOperation { | ||
| @doc("Unique identifier for the resource involved in the operation, for example Azure resource ID") | ||
| resourceId?: armResourceIdentifier; |
| description: string; | ||
|
|
||
| @doc("The type of resources used in the start request eg virtual machines") | ||
| @doc("The type of resources used in the request eg virtual machines") |
There was a problem hiding this comment.
doc-only unversioned change (generally acceptable)
| @doc("The type of resources used in the deallocate request eg virtual machines") | ||
| type: string; | ||
| @doc("The execute-type request for power operations") | ||
| model ExecuteTypeRequest { |
There was a problem hiding this comment.
If this is only used as a mix-in (i.e ...ExecuteTypeRequest in other models) then this should be an alias, to prevent it from appearing in other api-versions
| @doc("The response from a start request") | ||
| model StartResourceOperationResponse { | ||
| @doc("Common model for operation response") | ||
| model OperationResponse { |
There was a problem hiding this comment.
If this is only used to mix in to other model types, you should model this as an alias. This will porevent the type showing up in previous versions.
…sallow breaking change from the previous preview version.
1) Added loosely typed json for baseProfile and resourceOverrides
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.