Edit securityContact swagger for 2020-01-01#12265
Conversation
|
Hi, @ovedti 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 |
|---|---|
1010 - AddingRequiredParameter |
The required parameter 'securityContact' was added in the new version. New: Microsoft.Security/preview/2020-01-01-preview/securityContacts.json#L125:9 |
1011 - AddingResponseCode |
The new version adds a response code '200'. New: Microsoft.Security/preview/2020-01-01-preview/securityContacts.json#L146:11 |
️️✔️LintDiff succeeded [Detail] [Expand]
Validation passes for LintDiff.
️⚠️Avocado: 1 Warnings warning [Detail]
| Rule | Message |
|---|---|
| The default tag contains multiple API versions swaggers. readme: specification/security/resource-manager/readme.md tag: specification/security/resource-manager/readme.md#tag-package-composite-v3 |
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️[Staging] Cross Version BreakingChange (Base on preview version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️[Staging] Cross Version BreakingChange (Base on stable version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
Swagger Generation Artifacts
|
|
I see that this PR raised a "breaking chage" flag, but it is actually has not been published yet. |
|
Hi @ovedti, 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. |
867c650 to
4158e2d
Compare
|
hi @msyyc could you pls help confirm impact to Python SDK? |
It's ok for python |
|
Go breaking changes are not introduced in this PR |
Thanks! I created an ADO, waiting for their response 👍 |
|
unfortunately, adding new statuscode to existing version is also breakingchange :( |
|
Hi @ovedti, Your PR has some issues. Please fix the CI sequentially by following the order of
|
...ecurity/resource-manager/Microsoft.Security/preview/2020-01-01-preview/securityContacts.json
Show resolved
Hide resolved
HI @ArcturusZhang @msyyc sorry the PR has new commit, which adding a new param to create call https://github.com/Azure/azure-rest-api-specs/pull/12265/files#diff-60a32dc7bc6d8e143ae6ecf7ab442860ae7666a2e0038ade276cf85d7bee3036R136. Could you pls re-evaluate impact to Go and Python SDKs? thanks |
hi @msyyc @ArcturusZhang could you pls confirm impact to Python and GO SDK? thanks |
|
@yungezz this PR does not introduce breaking changes to go SDK |
|
|
This PR is ok for Python |
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 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.