[Hub Generated] Review request for Microsoft.HybridCompute to add version preview/2022-08-11-preview#20502
Conversation
…022-05-10-preview to version 2022-08-11-preview
|
Hi, @ankjayant 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
|
Swagger Generation Artifacts
|
Generated ApiView
|
|
Hi @ankjayant, 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. |
|
@ankjayant - Ensure you have examples for the new API in the PR |
|
Hi @ankjayant, Your PR has some issues. Please fix the CI sequentially by following the order of
|
d8e5760 to
6edca07
Compare
|
Hi, @ankjayant your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
25c83bc to
289c8b5
Compare
| }, | ||
| "description": "The List Extension Metadata response." | ||
| }, | ||
| "ExtensionValue": { |
There was a problem hiding this comment.
There was a problem hiding this comment.
I am a little confused as to what you mean by replacing the proxyresource definition, can you elaborate on the issue a little further and tell me what needs to get done to resolve it?
There was a problem hiding this comment.
At commit 12 this definition included a $ref to v1 common types definition ProxyResource which has the required top-level properties id, name, and type. Now that $ref is gone, and an id and name property are added in this definition. Recommendation to fix it is to add a $ref to the ProxyResource definition in v3 common types and remove the id and name from this definition.
There was a problem hiding this comment.
@mentat9 - Thank you Chris.
Updated to include ProxyResource v3 common-type.
Lmk if this looks good
Update readme.python.md
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.