[Hub Generated] Publish private branch 'prateekyadavMS-maintenance-prateek-Microsoft.Maintenance-2023-09-01-preview' #26185
Conversation
This file contains 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
…-04-01 to version 2023-09-01-preview
|
The PR is created based on the updates in the private branch. The updates in the PR has already been reviewed and approved with this PR Azure/azure-rest-api-specs-pr/14097 |
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 Validation Report
|
| compared swaggers (via Oad v0.10.4)] | new version | base version |
|---|---|---|
| Maintenance.json | 2023-09-01-preview(9e02b66) | 2023-04-01(main) |
| Maintenance.json | 2023-09-01-preview(9e02b66) | 2022-11-01-preview(main) |
The following breaking changes are detected by comparison with the latest preview version:
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 3 Warnings warning [Detail]
| compared tags (via openapi-validator v2.1.6) | new version | base version |
|---|---|---|
| package-preview-2023-09 | package-preview-2023-09(9e02b66) | default(main) |
[must fix]The following errors/warnings are introduced by current PR:
| Rule | Message | Related RPC [For API reviewers] |
|---|---|---|
| Not using the common-types defined parameter 'resourceGroupName'. Location: Microsoft.Maintenance/preview/2023-09-01-preview/Maintenance.json#L285 |
||
| Not using the common-types defined parameter 'subscriptionId'. Location: Microsoft.Maintenance/preview/2023-09-01-preview/Maintenance.json#L285 |
||
| Not using the common-types defined parameter 'api-version'. Location: Microsoft.Maintenance/preview/2023-09-01-preview/Maintenance.json#L285 |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
Swagger Generation Artifacts
|
Generated ApiView
|
AzureRestAPISpecReview
added
ARMReview
new-api-version
ReadyForApiTest
This was referenced Oct 12, 2023
ms-zhenhua
added
ARMSignedOff
prateekyadavMS
added
the
DoNotMerge
prateekyadavMS
requested review from
KalpeshChavan12
and removed request for
KalpeshChavan12
KalpeshChavan12
approved these changes
Oct 16, 2023
prateekyadavMS
removed
the
DoNotMerge
ms-zhenhua
deleted the
published/Azure/azure-rest-api-specs-pr/prateekyadavMS-maintenance-prateek-Microsoft.Maintenance-2023-09-01-preview
branch
|
Swagger pipeline restarted successfully, please wait for status update in this comment. |
This was referenced Oct 16, 2023
jnlycklama
pushed a commit
that referenced
this pull request
Nov 8, 2023
…ateek-Microsoft.Maintenance-2023-09-01-preview' (#26185) * Adds base for updating Microsoft.Maintenance from version stable/2023-04-01 to version 2023-09-01-preview * Updates readme * Updates API version in new specs and examples * example add * Maintenance.json change for put * changes * changes * 201 and 202 * Location + provisioning state * Removed "404" and 409 due to NoErrorCodeResponses * LroErrorContent * Remove "202", provisioning state * Adding all responses in examples * "applyUpdate" not "ApplyUpdate" * "status" not "Status" * Example to cover VMSS with new version * prettier changes on new example file
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.
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.