-
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
Improve AKS Swagger documentation #14696
Conversation
Hi, @matthchr 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. vsswagger@microsoft.com |
Swagger Validation Report
|
Rule | Message |
---|---|
'osDiskSizeGB' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.ContainerService/stable/2021-05-01/managedClusters.json#L2327 |
|
'osDiskType' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.ContainerService/stable/2021-05-01/managedClusters.json#L2330 |
|
'kubeletDiskType' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.ContainerService/stable/2021-05-01/managedClusters.json#L2333 |
|
'osType' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.ContainerService/stable/2021-05-01/managedClusters.json#L2351 |
|
'osSKU' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.ContainerService/stable/2021-05-01/managedClusters.json#L2354 |
|
'type' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.ContainerService/stable/2021-05-01/managedClusters.json#L2371 |
|
'mode' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.ContainerService/stable/2021-05-01/managedClusters.json#L2374 |
|
'osType' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.ContainerService/stable/2021-05-01/managedClusters.json#L3657 |
|
'osType' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.ContainerService/stable/2021-05-01/managedClusters.json#L3978 |
The following errors/warnings exist before current PR submission:
Only 10 items are listed, please refer to log for more details.
Rule | Message |
---|---|
R2026 - AvoidAnonymousTypes |
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/stable/2021-05-01/managedClusters.json#L2491 |
R2026 - AvoidAnonymousTypes |
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/stable/2021-05-01/managedClusters.json#L2584 |
R2026 - AvoidAnonymousTypes |
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/stable/2021-05-01/managedClusters.json#L3208 |
R2026 - AvoidAnonymousTypes |
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/stable/2021-05-01/managedClusters.json#L3456 |
R2026 - AvoidAnonymousTypes |
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/stable/2021-05-01/managedClusters.json#L3580 |
R2026 - AvoidAnonymousTypes |
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/stable/2021-05-01/managedClusters.json#L3623 |
R4009 - RequiredReadOnlySystemData |
The response of operation:'ManagedClusters_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.ContainerService/stable/2021-05-01/managedClusters.json#L420 |
R4009 - RequiredReadOnlySystemData |
The response of operation:'AgentPools_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.ContainerService/stable/2021-05-01/managedClusters.json#L892 |
R4009 - RequiredReadOnlySystemData |
The response of operation:'PrivateEndpointConnections_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.ContainerService/stable/2021-05-01/managedClusters.json#L1448 |
R4009 - RequiredReadOnlySystemData |
The response of operation:'ManagedClusters_CreateOrUpdate' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.ContainerService/stable/2021-05-01/managedClusters.json#L460 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
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.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
[Staging] SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
|:speech_balloon: AutorestCore/Exception|"readme":"containerservice/resource-manager/readme.md",
"tag":"package-2021-05",
"details":"> Installing AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0)"|
|:speech_balloon: AutorestCore/Exception|"readme":"containerservice/resource-manager/readme.md",
"tag":"package-2021-05",
"details":"> Installed AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0->1.8.0)"|
The following errors/warnings exist before current PR submission:
|:speech_balloon: AutorestCore/Exception|"readme":"containerservice/resource-manager/readme.md",
"tag":"package-2021-05",
"details":"> Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)"|
|:speech_balloon: AutorestCore/Exception|"readme":"containerservice/resource-manager/readme.md",
"tag":"package-2021-05-01-only",
"details":"> Loading AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0->1.8.0)"|
|:speech_balloon: AutorestCore/Exception|"readme":"containerservice/resource-manager/readme.md",
"tag":"package-2021-05-01-only",
"details":"> Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)"|
️️✔️
[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
[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. |
Swagger Generation Artifacts
|
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Outdated
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Outdated
Show resolved
Hide resolved
Hi @matthchr, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Outdated
Show resolved
Hide resolved
}, | ||
"gpuInstanceProfile": { | ||
"$ref": "#/definitions/GPUInstanceProfile", | ||
"description": "GPUInstanceProfile to be used to specify GPU MIG instance profile for supported GPU VM SKU. Supported values are MIG1g, MIG2g, MIG3g, MIG4g and MIG7g." | ||
"description": "GPUInstanceProfile to be used to specify GPU MIG instance profile for supported GPU VM SKU." |
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.
This is a lot of abbreviations. When can this be set? What is it for ? What does it enable? Needs significant clarification.
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.
Usually API argument doc is a brief introduction. It doesn't cover full details of the usage, which will be covered by feature doc. But the supported values should be kept to make it easier to use.
@qinchen352 FYI.
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.
@xuto2 - The type being ref
'ed is an enum with these values. As you can see in the REST API Docs and in the Python SDK when something is defined as an enum it already gets a list of supported values following it.
In the case of most SDKs (including Python) this results in the awkward:
GPUInstanceProfile to be used to specify GPU MIG instance profile
for supported GPU VM SKU. Supported values are MIG1g, MIG2g, MIG3g, MIG4g and MIG7g. Possible
values include: "MIG1g", "MIG2g", "MIG3g", "MIG4g", "MIG7g".
Where we say the same thing twice in a row.
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Outdated
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Outdated
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Outdated
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Outdated
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Outdated
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Show resolved
Hide resolved
...erservice/resource-manager/Microsoft.ContainerService/stable/2021-05-01/managedClusters.json
Show resolved
Hide resolved
24ed8eb
to
b8a60d3
Compare
2217814
to
f47bd2c
Compare
e4acda5
to
df422a6
Compare
df422a6
to
4655fad
Compare
4655fad
to
0f75def
Compare
0f75def
to
d979edd
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Closed this PR and opened #14934 to clear breaking change tags that are no longer appropriate as all breaking changes have been removed. |
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Please ensure to add changelog with 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
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
Please 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 there are following updates in the PR, ensure to request an approval from 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.