Review request for Microsoft.ContainerService to add version 2022-01-02-preview #17579
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
…w/2021-11-01-preview to version 2022-01-02-preview
* update readme to help generate SDK * update readme * fix golang readme * fix tag
* Add adminUsers in aadprofile * Update description
…#17211) * Support query parameter 'format' in listClusterUserCredential handler * Fix lint * Fix typo
* Add property HostGroupID and its examples * fix format issue * add more details for Dedicated host group Co-authored-by: Jianping Zeng <[email protected]>
|
Hi, @FumingZhang Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected] |
|
Swagger pipeline can not start as the pull request has merge conflicts. |
1 similar comment
|
Swagger pipeline can not start as the pull request has merge conflicts. |
|
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
FumingZhang
changed the title
25 tasks
Swagger Validation Report
|
| Rule | Message |
|---|---|
|
Inline/anonymous models must not be used, instead define a schema with a model name in the 'definitions' section and refer to it. This allows operations to share the models. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2849 |
|
Inline/anonymous models must not be used, instead define a schema with a model name in the 'definitions' section and refer to it. This allows operations to share the models. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2942 |
|
Inline/anonymous models must not be used, instead define a schema with a model name in the 'definitions' section and refer to it. This allows operations to share the models. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L4135 |
|
The response of operation:'ManagedClusters_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L428 |
|
The response of operation:'AgentPools_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L930 |
|
The response of operation:'PrivateEndpointConnections_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L1507 |
|
The response of operation:'ManagedClusters_CreateOrUpdate' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L468 |
|
The response of operation:'AgentPools_CreateOrUpdate' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L977 |
|
The response of operation:'PrivateEndpointConnections_Update' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L1555 |
|
The response of operation:'ManagedClusters_UpdateTags' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L593 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L1211 |
|
The delete operation is defined without a 200 or 204 error response implementation,please add it.' Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L663 |
|
The delete operation is defined without a 200 or 204 error response implementation,please add it.' Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L1118 |
|
The response schema of operations API '/providers/Microsoft.ContainerService/operations' does not match the ARM specification. Please standardize the schema. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L37 |
|
The private endpoint model 'PrivateLinkResourcesListResult' schema does not conform to the common type definition. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L4952 |
|
The schema 'OperationListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2240 |
|
The schema 'OperationValue' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2253 |
|
The schema 'OperationValueDisplay' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2273 |
|
The schema 'Resource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2298 |
|
The schema 'SubResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2337 |
|
The schema 'TagsObject' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2358 |
|
The schema 'ManagedClusterServicePrincipalProfile' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2577 |
|
The schema 'ContainerServiceMasterProfile' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2593 |
|
The schema 'ManagedClusterAgentPoolProfileProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2647 |
|
The schema '1' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2849 |
|
The schema 'AgentPoolListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2910 |
|
The schema 'AgentPoolUpgradeSettings' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2927 |
|
The schema '1' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2942 |
|
The schema 'ManagedClusterWindowsProfile' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L2954 |
|
The schema 'ContainerServiceLinuxProfile' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.ContainerService/preview/2022-01-02-preview/managedClusters.json#L3020 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️~[Staging] ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️Cross-Version Breaking Changes succeeded [Detail] [Expand]
There are no breaking changes.
- Compared Swaggers (Based on Oad v0.9.1)
- current:preview/2022-01-02-preview/managedClusters.json compared with base:stable/2021-10-01/managedClusters.json
- current:preview/2022-01-02-preview/managedClusters.json compared with base:preview/2021-11-01-preview/managedClusters.json
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
️️✔️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).
Swagger Generation Artifacts
|
This was referenced Feb 7, 2022
FumingZhang
requested review from
ArcturusZhang,
BigCat20196 and
msyyc
as code owners
FumingZhang
added
the
WaitForARMFeedback
|
approved for python breaking change |
pilor
added
ARMSignedOff
FumingZhang
added
the
DoNotMerge
|
We are waiting for the arm manifest to finish rolling out. Temporarily block merge. |
FumingZhang
removed
the
DoNotMerge
|
We have finished the rollout of our arm manifest. Please help merge this PR @ruowan. Thanks! |
ruowan
approved these changes
Feb 10, 2022
This was referenced Feb 10, 2022
This was referenced Feb 11, 2022
FredericHeem
pushed a commit
to grucloud/azure-rest-api-specs
that referenced
this pull request
Mar 7, 2022
…02-preview (Azure#17579) * Adds base for updating Microsoft.ContainerService from version preview/2021-11-01-preview to version 2022-01-02-preview * Updates readme * Updates API version in new specs and examples * Add NetworkPlugin none option (Azure#17393) * Update readme to help generate SDK (Azure#17372) * update readme to help generate SDK * update readme * fix golang readme * fix tag * Add adminUsers in aadprofile (Azure#17367) * Add adminUsers in aadprofile * Update description * Support query parameter 'format' in listClusterUserCredential handler (Azure#17211) * Support query parameter 'format' in listClusterUserCredential handler * Fix lint * Fix typo * Add property HostGroupID and its examples (Azure#17459) * Add property HostGroupID and its examples * fix format issue * add more details for Dedicated host group Co-authored-by: Jianping Zeng <[email protected]> * Revert "Add adminUsers in aadprofile (Azure#17367)" (Azure#17522) This reverts commit ba6e656. * fix conflict (Azure#17624) Co-authored-by: Matt Stam <[email protected]> Co-authored-by: Tongyao Si <[email protected]> Co-authored-by: Jianping Zeng <[email protected]> Co-authored-by: Jianping Zeng <[email protected]>
FumingZhang
deleted the
dev-containerservice-Microsoft.ContainerService-2022-01-02-preview
branch
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.
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.