-
Notifications
You must be signed in to change notification settings - Fork 5.6k
KubernetesConfiguration identity property bug fix #13264
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
Conversation
|
Hi, @safeermohammed 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
|
| Rule | Message |
|---|---|
1033 - RemovedProperty |
The new version is missing a property found in the old version. Was 'identity' renamed or removed? New: Microsoft.KubernetesConfiguration/preview/2020-07-01-preview/extensions.json#L552:11 Old: Microsoft.KubernetesConfiguration/preview/2020-07-01-preview/extensions.json#L552:11 |
1041 - AddedPropertyInResponse |
The new version has a new property 'identity' in response that was not found in the old version. New: Microsoft.KubernetesConfiguration/preview/2020-07-01-preview/extensions.json#L547:7 Old: Microsoft.KubernetesConfiguration/preview/2020-07-01-preview/extensions.json#L547:7 |
️️✔️LintDiff succeeded [Detail] [Expand]
Validation passes for LintDiff.
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️[Staging] Cross Version BreakingChange (Base on preview version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️[Staging] Cross Version BreakingChange (Base on stable version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️[Staging] SDK Track2 Validation: 16 Warnings warning [Detail]
Only 10 items are listed, please refer to log for more details.
- The following tags are being changed in this PR
| Rule | Message |
|---|---|
| "readme":"kubernetesconfiguration/resource-manager/readme.md", "tag":"package-2020-07-01-preview", "details":"The schema 'Result' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"kubernetesconfiguration/resource-manager/readme.md", "tag":"package-2020-07-01-preview", "details":"The schema 'ErrorResponse' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"kubernetesconfiguration/resource-manager/readme.md", "tag":"package-2020-07-01-preview", "details":"The schema 'ErrorDefinition' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"kubernetesconfiguration/resource-manager/readme.md", "tag":"package-2020-07-01-preview", "details":"The schema 'ConfigurationProtectedSettings' with an undefined type and additionalProperties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"kubernetesconfiguration/resource-manager/readme.md", "tag":"package-2020-07-01-preview", "details":"The schema 'SourceControlConfiguration' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"kubernetesconfiguration/resource-manager/readme.md", "tag":"package-2020-07-01-preview", "details":"The schema 'SourceControlConfigurationList' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"kubernetesconfiguration/resource-manager/readme.md", "tag":"package-2020-07-01-preview", "details":"The schema 'ResourceProviderOperation' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"kubernetesconfiguration/resource-manager/readme.md", "tag":"package-2020-07-01-preview", "details":"The schema 'ResourceProviderOperation-display' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"kubernetesconfiguration/resource-manager/readme.md", "tag":"package-2020-07-01-preview", "details":"The schema 'ResourceProviderOperationList' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"kubernetesconfiguration/resource-manager/readme.md", "tag":"package-2020-07-01-preview", "details":"The schema 'ConfigurationSettings' with an undefined type and additionalProperties is a bit ambigious. This has been auto-corrected to 'type:object'" |
️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
Swagger Generation Artifacts
|
|
Hi @safeermohammed, Your PR has some issues. Please fix the CI sequentially by following the order of
|
|
Hi @safeermohammed, 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. |
|
Note to reviewers, Preview API, Identity property was incorrectly specified inside resource properties bag in swagger. CLI/SDK etc are not generated yet for this resource |
860f137 to
499a657
Compare
filizt
left a comment
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. However you still need to go through the breaking changes review process which is not part of the ARM API review. Please see above for the instructions for that.
|
Hi, @safeermohammed. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
|
Hi, @safeermohammed. The PR will be closed since the PR has no update for 28 days. If you still need the PR review to proceed, please reopen it and @ mention PR assignee. |
|
Hi, @safeermohammed. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days. |
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.
What's the purpose of the update?
When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
This is preview API already in production. Issue only with swagger
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
Swagger was merged on 2/28. No CLI yet
If it's an update to existing version, please select SDKs of specific language and CLIs that require refresh after swagger is published.
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.