-
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
[Hub Generated] Review request for Microsoft.KubernetesConfiguration to add version stable/2022-07-01 #19384
Conversation
… stable/2022-03-01 to version 2022-07-01
Hi, @summerhasama 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. vscswagger@microsoft.com |
1 similar comment
Hi, @summerhasama 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. vscswagger@microsoft.com |
Swagger Validation Report
|
Rule | Message |
---|---|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: clientCertificateSendChain Location: Microsoft.KubernetesConfiguration/stable/2022-07-01/fluxconfiguration.json#L791 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: clientCertificateSendChain Location: Microsoft.KubernetesConfiguration/stable/2022-07-01/fluxconfiguration.json#L831 |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: forceDelete Location: Microsoft.KubernetesConfiguration/stable/2022-07-01/extensions.json#L192 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: forceDelete Location: Microsoft.KubernetesConfiguration/stable/2022-07-01/fluxconfiguration.json#L264 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: insecure Location: Microsoft.KubernetesConfiguration/stable/2022-07-01/fluxconfiguration.json#L569 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: insecure Location: Microsoft.KubernetesConfiguration/stable/2022-07-01/fluxconfiguration.json#L615 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: prune Location: Microsoft.KubernetesConfiguration/stable/2022-07-01/fluxconfiguration.json#L905 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: force Location: Microsoft.KubernetesConfiguration/stable/2022-07-01/fluxconfiguration.json#L910 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: prune Location: Microsoft.KubernetesConfiguration/stable/2022-07-01/fluxconfiguration.json#L954 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: force Location: Microsoft.KubernetesConfiguration/stable/2022-07-01/fluxconfiguration.json#L959 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌
ApiReadinessCheck: 1 Errors, 0 Warnings failed [Detail]
Rule | Message |
---|---|
API Readiness check failed. Please make sure your service is deployed. |
"code: InvalidResourceType, message: The resource type 'operations' could not be found in the namespace 'Microsoft.KubernetesConfiguration' for api version '2022-07-01'. The supported api-versions are '2019-11-01-preview, 2020-07-01-preview, 2020-10-01-preview, 2021-03-01, 2021-05-01-preview, 2021-06-01-preview, 2021-09-01, 2021-11-01-preview, 2021-12-01-preview, 2022-01-01-preview, 2022-03-01'." |
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️⚠️
Cross-Version Breaking Changes: 11 Warnings warning [Detail]
- Compared Swaggers (Based on Oad v0.9.5)
- current:stable/2022-07-01/extensions.json compared with base:stable/2022-03-01/extensions.json
- current:stable/2022-07-01/extensions.json compared with base:preview/2022-04-02-preview/extensions.json
- current:stable/2022-07-01/fluxconfiguration.json compared with base:stable/2022-03-01/fluxconfiguration.json
- current:stable/2022-07-01/fluxconfiguration.json compared with base:preview/2022-01-01-preview/fluxconfiguration.json
- current:stable/2022-07-01/kubernetesconfiguration.json compared with base:stable/2022-03-01/kubernetesconfiguration.json
- current:stable/2022-07-01/kubernetesconfiguration.json compared with base:preview/2022-01-01-preview/kubernetesconfiguration.json
- current:stable/2022-07-01/operations.json compared with base:stable/2022-03-01/operations.json
- current:stable/2022-07-01/operations.json compared with base:preview/2022-01-01-preview/operations.json
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️
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
|
Hi, @summerhasama your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
1 similar comment
Hi, @summerhasama your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
...ration/resource-manager/Microsoft.KubernetesConfiguration/common/2022-07-01/definitions.json
Outdated
Show resolved
Hide resolved
...uration/resource-manager/Microsoft.KubernetesConfiguration/stable/2022-07-01/extensions.json
Outdated
Show resolved
Hide resolved
Added a few comments. Please remove the "ARMChangesRequested" label when you want the API reviewer to look at this review again |
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.
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.
🚀
…r Microsoft.KubernetesConfiguration to add version stable/2022-07-01 (#2423) Create to sync Azure/azure-rest-api-specs#19384 [ReCreate this PR](https://github.com/azure-resource-manager-schemas/compare/main...azure-sdk:sdkAuto/kubernetesconfiguration?expand=1)
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM API Information (Control Plane)
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist (MS Employees Only):
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 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 copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For 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 you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.