-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
aks fleet list credentials api #19559
aks fleet list credentials api #19559
Conversation
Hi, @haitch 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 Validation Report
|
compared tags (via openapi-validator v1.13.0) | new version | base version |
---|---|---|
package-preview-2022-06 | package-preview-2022-06(f095fb1) | package-preview-2022-06(dev-containerservice-Microsoft.ContainerService-2022-06-02-preview) |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
The child tracked resource, 'members' with immediate parent 'Fleet', must have a list by immediate parent operation. Location: Microsoft.ContainerService/preview/2022-06-02-preview/fleets.json#L685 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️⚠️
SDK Track2 Validation: 2 Warnings warning [Detail]
- The following tags are being changed in this PR
Rule | Message |
---|---|
"readme":"containerservice/resource-manager/readme.md", "tag":"package-preview-2022-06", "details":"Semantic violation: Sibling values alongside $ref will be ignored. See https://github.com/Azure/autorest/blob/main/docs/openapi/howto/$ref-siblings.md for allowed values (components > schemas > ManagedClusterPropertiesForSnapshot > properties > sku)\n keys: [ \u001b[32m'type'\u001b[39m ]" |
|
"readme":"containerservice/resource-manager/readme.md", "tag":"package-preview-2022-06", "details":"Semantic violation: Sibling values alongside $ref will be ignored. See https://github.com/Azure/autorest/blob/main/docs/openapi/howto/$ref-siblings.md for allowed values (components > schemas > ManagedClusterPropertiesForSnapshot > properties > networkProfile)\n keys: [ \u001b[32m'type'\u001b[39m ]" |
|
💬 | "readme":"containerservice/resource-manager/readme.md", "tag":"package-preview-2022-06", "details":"> Installing AutoRest extension '@microsoft.azure/openapi-validator' (1.11.0 -> 1.11.0)" |
💬 | "readme":"containerservice/resource-manager/readme.md", "tag":"package-preview-2022-06", "details":"> Installed AutoRest extension '@microsoft.azure/openapi-validator' (1.11.0->1.11.0)" |
💬 | "readme":"containerservice/resource-manager/readme.md", "tag":"package-preview-2022-06", "details":"> Installing AutoRest extension '@autorest/modelerfour' (4.21.4 -> 4.21.4)" |
💬 | "readme":"containerservice/resource-manager/readme.md", "tag":"package-preview-2022-06", "details":"> Installed AutoRest extension '@autorest/modelerfour' (4.21.4->4.21.4)" |
💬 | "readme":"containerservice/resource-manager/readme.md", "tag":"package-preview-2022-06", "details":"Autorest completed in 14.45s. 0 files generated." |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
"readme":"containerservice/resource-manager/readme.md", "tag":"package-preview-2022-06", "details":"Using directive.0.suppress which is deprecated and will be removed in the future." |
|
"readme":"containerservice/resource-manager/readme.md", "tag":"package-preview-2022-06", "details":"Using directive.1.suppress which is deprecated and will be removed in the future." |
|
"readme":"containerservice/resource-manager/readme.md", "tag":"package-preview-2022-06", "details":"Semantic violation: Sibling values alongside $ref will be ignored. See https://github.com/Azure/autorest/blob/main/docs/openapi/howto/$ref-siblings.md for allowed values (components > schemas > Resource > properties > systemData)\n keys: [ \u001b[32m'type'\u001b[39m ]" |
|
💬 | "readme":"containerservice/resource-manager/readme.md", "tag":"package-preview-2022-06", "details":"AutoRest core version selected from configuration: ^3.2.0." |
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
Swagger Generation Artifacts
|
Hi @haitch, Your PR has some issues. Please fix the CI sequentially by following the order of
|
...erservice/resource-manager/Microsoft.ContainerService/preview/2022-06-02-preview/fleets.json
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/preview/2022-06-02-preview/fleets.json
Outdated
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/preview/2022-06-02-preview/fleets.json
Outdated
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/preview/2022-06-02-preview/fleets.json
Outdated
Show resolved
Hide resolved
...ource-manager/Microsoft.ContainerService/preview/2022-06-02-preview/examples/Fleets_Get.json
Outdated
Show resolved
Hide resolved
Hi, @haitch your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board([email protected]). |
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.
LGTM
83f13e9
into
dev-containerservice-Microsoft.ContainerService-2022-06-02-preview
…02-preview (#19653) * Adds base for updating Microsoft.ContainerService from version preview/2022-05-02-preview to version 2022-06-02-preview * Updates readme * Updates API version in new specs and examples * update readmes (#19422) * Containerservice 2022 06 02 preview fleet (#19541) * add fleets and fleet members resource types * remove clusterLocation * wording * don't flatten hubprofile * extra comma * fix patch example * Fix violated rule R4041 for 2022-06-02-preview managedCluster swagger (#19582) * remove useless directive * fix R4041 * fix * add node restriction to swagger (#19587) * aks fleet list credentials api (#19559) * add fleet list credential api * tweaks * fix example filename * fix casing * add resourceId on hubProfile * drop the new field, keep it as internal field * fix duplicate shema error * different name for fleet credential results * use xms-identifier on the array items * prettier fi Co-authored-by: Stephane Erbrech <[email protected]> * sterbrec - address fleet comments - Microsoft.ContainerService - 2022-06-02-preview (#19783) * address fleet comments * add example for nadditional status code * Add missing `x-ms-long-running-operation-options` for delete operations in fleet-related API (#19787) * add final-state-via * fix final state to location header Co-authored-by: Stéphane Erbrech <[email protected]> Co-authored-by: lht6 <[email protected]> Co-authored-by: Haitao Chen <[email protected]>
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 appy to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
-[ ] 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.