Add delete incident comment API#11297
Conversation
|
You don't have permission to trigger SDK Automation. |
|
Thank you for your contribution roherzbe! We will review the pull request and get back to you soon. |
|
Hi, @roherzbe 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 |
|
Hi, @roherzbe your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). cc @leni-msft |
|
Hi @leni-msft, According to the automatic validations it marks that there are 6 Errors & Breaking Changes, all other validations have passed successfully (as far as I can tell). Can you please help me understand why these changes are breaking? Thanks in advance, |
| } | ||
| ], | ||
| "responses": { | ||
| "200": { |
There was a problem hiding this comment.
Are these swagger bugfixes to bring swagger in-line with how the API has always behaved? If not, these should go into a new api-version as the existing preview version is almost 2 years old.
There was a problem hiding this comment.
Yes, this is a bug fix. It exists in production for more then half a year and has no costumer impact (not breaking any scenario). We are aware that in the stable version this kind of change will require a new version.
pilor
left a comment
There was a problem hiding this comment.
Swagger fixes for API surface that was already present. Please work with @leni-msft to deal with any SDK breaking issues and for merging this
|
@pilor Thank you very much! |
|
Hi @roherzbe, one or multiple breaking change(s) is detected in your PR. Pls follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
|
@roherzbe please follow the breaking change review process above。 |
|
Hi @leni-msft |
|
@roherzbe Adding response code belongs to API behavioral changes. To proceed, please follow the section |
|
@JeffreyRichter |
|
Jeffrey, Thank you very much! |
|
/azp run automation - sdk |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Azure CLI Extension Generation - Release
|
azure-sdk-for-java - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-go - Release
|
azure-sdk-for-net - Release
|
azure-sdk-for-python - Release
|
azure-resource-manager-schemas - Release
|
azure-sdk-for-python-track2 - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Trenton Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
* Add delete incident comment * Fix for Prettier * Fix Prettier 2
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
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.
Please follow the link to find more details on PR review process.