-
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
Update batch dataplane for version 2021-01-01-13.0 - Data Plane #12426
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 |
Swagger Validation Report
|
Rule | Message |
---|---|
"readme":"batch/data-plane/readme.md", "tag":"package-2021-01.13.0", "details":"The schema 'PoolUsageMetrics' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"batch/data-plane/readme.md", "tag":"package-2021-01.13.0", "details":"The schema 'PoolListUsageMetricsResult' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"batch/data-plane/readme.md", "tag":"package-2021-01.13.0", "details":"The schema 'ImageInformation' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"batch/data-plane/readme.md", "tag":"package-2021-01.13.0", "details":"The schema 'AuthenticationTokenSettings' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"batch/data-plane/readme.md", "tag":"package-2021-01.13.0", "details":"The schema 'AccountListSupportedImagesResult' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"batch/data-plane/readme.md", "tag":"package-2021-01.13.0", "details":"The schema 'UsageStatistics' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"batch/data-plane/readme.md", "tag":"package-2021-01.13.0", "details":"The schema 'ResourceStatistics' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"batch/data-plane/readme.md", "tag":"package-2021-01.13.0", "details":"The schema 'PoolStatistics' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"batch/data-plane/readme.md", "tag":"package-2021-01.13.0", "details":"The schema 'JobStatistics' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"batch/data-plane/readme.md", "tag":"package-2021-01.13.0", "details":"The schema 'NameValuePair' with an undefined type and decalared properties 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, @paterasMSFT your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). cc @tjprescott |
This PR was split off from #12393 (which contained both data and management planes previously). Added @anuchandy as the reviewer since he has already reviewed these changes in the other PR. We're in a bit of a holding pattern here while we sort through an issue on the service side with VM extensions, so marked this as not ready for review. Will update when we have things sorted on our end. |
44a2c13
to
32ec4dd
Compare
32ec4dd
to
487da4b
Compare
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
Marked as DoNotMerge until the issue with virtual machine extensions is resolved on the service side. (Even though this likely won't affect the data plane swagger) |
Hi, @paterasMSFT. 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, @paterasMSFT. 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 @anuchandy. |
Hi, @paterasMSFT. 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. |
2 similar comments
Hi, @paterasMSFT. 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. |
Hi, @paterasMSFT. 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. |
New features in this release are:
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 API 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.