-
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
OSSRDBMS Swagger completeness related changes #11685
Conversation
Thank you for your contribution shinilm! We will review the pull request and get back to you soon. |
Swagger Generation Artifacts
|
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
Hi @shinilm, 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. |
Hi, @shinilm 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] |
...anager/Microsoft.DBforMariaDB/preview/2018-06-01-preview/examples/RecoverableServersGet.json
Show resolved
Hide resolved
...tion/mariadb/resource-manager/Microsoft.DBforMariaDB/preview/2018-06-01-preview/mariadb.json
Show resolved
Hide resolved
"$ref": "./examples/RecoverableServersGet.json" | ||
} | ||
}, | ||
"description": "Gets a recoverable MariaDB Server.", |
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.
Same comments as the preview version.
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.
This is what service returns
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.
This is to make old api version and swagger aligned. Signing from ARM side.
Hi Erich,
The ARM team and the Breaking change board approved the PR. Please help merge this PR.
Thanks
Shinil
From: erich-wang <[email protected]>
Sent: Wednesday, November 18, 2020 9:24 PM
To: Azure/azure-rest-api-specs <[email protected]>
Cc: Shinil Mannadath <[email protected]>; Author <[email protected]>
Subject: Re: [Azure/azure-rest-api-specs] OSSRDBMS Swagger completeness related changes (#11685)
/azp run
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F11685%23issuecomment-730137384&data=04%7C01%7Cshinim%40microsoft.com%7C2a4d9f15f11d4b3454ee08d88c4b4ee4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637413602360425709%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=oOrfN0TAmBWnjlMuaCaWftsqYxT%2FYbpj1NHqJuls1uU%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKUG6JQ7HSOZKXMFU6V7LEDSQSTWVANCNFSM4TW2SIKA&data=04%7C01%7Cshinim%40microsoft.com%7C2a4d9f15f11d4b3454ee08d88c4b4ee4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637413602360435704%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=wC7fnrRMf7o4OWsXHShP4hQESkfUNEvhxdBXEIvHN%2FU%3D&reserved=0>.
|
* OSSRDBMS Swagger completeness related changes * OSSRDBMS Swagger completeness related changes * OSSRDBMS Swagger completeness related changes * OSSRDBMS Swagger completeness related changes
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
[X ] 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.