[Hub Generated] Review request for Microsoft.DesktopVirtualization to add version preview/2023-11-01-preview#26606
Merged
rkmanda merged 21 commits intoNov 28, 2023
Conversation
…review/2023-10-04-preview to version 2023-11-01-preview
Next Steps to Merge✔️ All automated merging requirements have been met! Refer to step 4 in the PR workflow diagram (even if your PR is for data plane, not ARM). |
Swagger Generation Artifacts
|
Generated ApiView
|
This was referenced Nov 8, 2023
Contributor
Author
|
The remaining LintDiff errors are all resourceNameRestriction checks for parameters that existed prior to this apiVersion and are currently in use. |
AzureRestAPISpecReview
added
ARMReview
WaitForARMFeedback
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
AzureRestAPISpecReview
added
ARMChangesRequested
BreakingChangeReviewRequired
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
This reverts commit 239d772.
ryanosh
added
WaitForARMFeedback
AzureRestAPISpecReview
added
ARMChangesRequested
and removed
WaitForARMFeedback
Contributor
Author
|
/azp run |
AzureRestAPISpecReview
removed
the
BreakingChangeReviewRequired
|
Azure Pipelines successfully started running 3 pipeline(s). |
ryanosh
added
WaitForARMFeedback
zizw123
added
the
ARMSignedOff
openapi-workflow-bot
Bot
removed
the
WaitForARMFeedback
Contributor
|
/azp run |
|
Swagger pipeline started successfully. If there is ApiView generated, it will be updated in this comment. |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Alancere
added
the
Approved-SdkBreakingChange-Go
Contributor
Author
|
Pushed a fix related to this issue https://stackoverflow.microsoft.com/questions/378322 |
Contributor
Author
|
/pr RequestMerge |
rkmanda
approved these changes
Nov 28, 2023
rkmanda
deleted the
ryanosh-desktopvirtualization-Microsoft.DesktopVirtualization-2023-11-01-preview
branch
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
5 participants
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.
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label
ARMChangesRequestedis removed from your PR. This should cause the label
WaitForARMFeedbackto be added.[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see
Getting helpsection below.Purpose of this PR
What's the purpose of this PR? Check all that apply. 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 Step 2, "ARM Review", for this PR.
Breaking changes review (Step 1)
you must follow the breaking changes process.
IMPORTANT This applies even if:
Such claims must be reviewed, and the process is the same.
ARM API changes review (Step 2)
ARMReviewlabel.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
Swagger-Suppression-Process
to get approval.
Getting help
and https://aka.ms/ci-fix.