-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fleet] API 2023-06-15-preview #25027
Conversation
…preview/2023-03-15-preview to version 2023-06-15-preview
* Adds base for updating Microsoft.ContainerService/fleet from version preview/2023-03-15-preview to version 2023-06-15-preview * Updates readme * Updates API version in new specs and examples * sync with ADO repo * exclude unneeded file changes * revert tsp config * revert helpers.tsp * remove package files * remove package files * add known word containerd * format * remove .npmrc * revert custom word * revert package-lock.json * re-generate json * add example * add example * fix read-only fields * fix read-only fields * re-generate json with latest compiler * add custom word back * re-generate json * restore config * add examples * add examples * add examples * add examples * add examples * add examples * prettier * fix examples * git ignore * review commoents * fix examples * make node image selection optional * fix warnings * fix warnings * fix warnings * fix docs * revert package changes * compile
Swagger Validation Report
|
compared swaggers (via Oad v0.10.4)] | new version | base version |
---|---|---|
fleets.json | 2022-09-02-preview(44f2bc2) | 2022-09-02-preview(main) |
fleets.json | 2023-03-15-preview(44f2bc2) | 2023-03-15-preview(main) |
️⚠️
Breaking Change(Cross-Version): 4 Warnings warning [Detail]
compared swaggers (via Oad v0.10.4)] | new version | base version |
---|---|---|
fleets.json | 2023-06-15-preview(44f2bc2) | 2023-03-15-preview(main) |
The following breaking changes are detected by comparison with the latest preview version:
Rule | Message |
---|---|
The new version adds a response code '202'. New: fleet/preview/2023-06-15-preview/fleets.json#L361:11 |
|
The new version adds a response code '202'. New: fleet/preview/2023-06-15-preview/fleets.json#L785:11 |
|
The new version has a different 'x-ms-longrunning-operation' value than the previous one. New: fleet/preview/2023-06-15-preview/fleets.json#L310:7 Old: fleet/preview/2023-03-15-preview/fleets.json#L310:7 |
|
The new version has a different 'x-ms-longrunning-operation' value than the previous one. New: fleet/preview/2023-06-15-preview/fleets.json#L724:7 Old: fleet/preview/2023-03-15-preview/fleets.json#L706:7 |
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
LintDiff succeeded [Detail] [Expand]
Validation passes for LintDiff.
compared tags (via openapi-validator v2.1.4) | new version | base version |
---|---|---|
package-2023-03-preview | package-2023-03-preview(44f2bc2) | package-2023-03-preview(main) |
package-2022-09-preview | package-2022-09-preview(44f2bc2) | package-2022-09-preview(main) |
package-2023-06-preview | package-2023-06-preview(44f2bc2) | default(main) |
️️✔️
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
|
Hi @zman-ms, this service has enabled Service API Toolset. All spec updates MUST be initiated from service ADO project repo, so that to guarantee it to be the source of truth., please review this pull request if it's intentional or reject it if it's not expected. Normally, all the specification or example changes should start with PR created in ADO. |
Hi, @zman-ms! Thank you for your pull request. To help get your PR merged: Generated ApiView comment added to this PR. You can use ApiView to show API versions diff. |
Hi @zman-ms! The automation detected breaking changes in this pull request. As a result, it added the |
Please address or respond to feedback from the ARM API reviewer. |
...ice/resource-manager/Microsoft.ContainerService/fleet/preview/2023-06-15-preview/fleets.json
Show resolved
Hide resolved
...ice/resource-manager/Microsoft.ContainerService/fleet/preview/2023-03-15-preview/fleets.json
Outdated
Show resolved
Hide resolved
@@ -255,12 +319,6 @@ interface UpdateRuns { | |||
IfNoneMatchParameters<UpdateRun> | |||
>; | |||
|
|||
@extension( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thought typespec had fixed this bug, and we could remove our override?
Next Steps to Merge |
Swagger pipeline restarted successfully, please wait for status update in this comment. |
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.
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 request review from an ARM API Review board.
ARM API changes review
ARMReview
label.ARMReview
label, if appropriate.If this happens, proceed according to guidance given in GitHub comments also added by the automation.
Breaking change review
If you have any breaking changes as defined in the Breaking Change Policy,
follow the process outlined in the High-level Breaking Change Process doc.
Getting help
and https://aka.ms/ci-fix.