Closed Raedalmalki250 closed 3 months ago
I don't understand if you open this by mistake, or if you're a bot. In any case, closing as inapplicable. If you are not a bot, and you meant to open this issue for this project, please explain and we can reopen.
For #28023 feedback.
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.
Click here to see the details of Step 1, Breaking Changes review
If you are in purview of Step 1 of the diagram, follow the [Breaking Changes review process]. **IMPORTANT!** This applies even if you believe your PR was mislabeled, for any reason, including tool failure.Click here to see the details of Step 2, ARM review
See https://aka.ms/azsdk/pr-arm-review.Click here to see the diagram footnotes
### Diagram footnotes [1] See [ARM review queue] (for **PR merge** queues, see [2]). [2] [public repo merge queue], [private repo merge queue] (for **ARM review** queue, [1]) The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.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:
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 ApiView` comment 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](https://aka.ms/azsdk/pr-suppressions) to get approval.Getting help
Purpose of this PR
andDue diligence checklist
.Next Steps to Merge
comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.queued
state, please add a comment with contents/azp run
. This should result in a new comment denoting aPR validation pipeline
has started and the checks should be updated after few minutes.Originally posted by @cataggar in https://github.com/Azure/azure-rest-api-specs/pull/28271