-
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
Batch DataPlane 2021-06-01.14 update #14830
Conversation
Hi, @paterasMSFT 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 |
[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 Validation Report
|
Swagger Generation Artifacts
|
Hi, @paterasMSFT your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently. Please create new branch with this recommendation for the review to continue. |
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.
Please go through the contribution checklist and ARM API Review Checklist added as part of the review and mark them completed. It will help you fix most of the issues and improve the quality of swagger and help close the PR faster. This is a requirement before review can be continued.
83f95d5
to
d4de940
Compare
Thank you. I created the PR as a draft as I hadn't done that yet. I will complete the checklist before I mark it ready for review.
I just rebased the branch on top of a commit with the required copy. Is it still necessary for me to create a new branch? |
0588942
to
9ae22aa
Compare
specification/batch/data-plane/Microsoft.Batch/stable/2021-06-01.14.0/BatchService.json
Outdated
Show resolved
Hide resolved
specification/batch/data-plane/Microsoft.Batch/stable/2021-06-01.14.0/BatchService.json
Outdated
Show resolved
Hide resolved
7280d8c
to
1af059b
Compare
@tjprescott could we get a review here? There's some urgency to it. Thank you! |
@chiragg4u would you mind approving your requested changes, so I can get a final approval from @tjprescott, who is assigned to the PR? |
@chiragg4u @dpwatrous you both requested changes. Please verify those have been made and approve so we can merge this PR. |
@chiragg4u looks good to me. Can you approve and merge? |
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.
These changes look good to me. 👍
I was originally concerned about the large number of "Cross Version Breaking Changes" reported by the tooling (> 500). But upon investigation it appears that all these are caused by the addition of type: object
to a schema that was already an object by virtue of having properties
, but the tool still reports this as a breaking change.
@tjprescott looks like we're ready to merge. |
@mikekistler or @JeffreyRichter, mind signing off on the validator "breaking changes" for the ControlPlane PR for this release as well, as they're essentially the same thing as on this one? Thanks! |
* Copy of 2020-09-01 for ease of review * Azure Batch updated to 2021-06-01.14 Suppressions Fixed property name. Fixed type Fixed casing Fixed casing Spelling fix Fixed enums Fixed enum Fixed EOF and casing from PR feedback Markdown fixes Added Managed Identity and Authentication Mode APIs. Fixed example Spot cleanup Casing fix Fixed spacing Added maxParallelTasks. Formatting. Removed newline Reverted markdown change to satisfy Avocado http://azure.github.io/autorest/user/literate-file-formats/configuration.html#the-file-format
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.