-
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
fix schema generation failure for securityinsights #10038
Conversation
[Staging] Swagger Validation Report
❌ |
Rule | Message |
---|---|
1032 - DifferentAllOf |
The new version has a different 'allOf' property than the previous one. New: Microsoft.SecurityInsights/stable/2020-01-01/SecurityInsights.json#L1704:9 Old: Microsoft.SecurityInsights/stable/2020-01-01/SecurityInsights.json#L1704:9 |
1034 - AddedRequiredProperty |
The new version has new required property 'state' that was not found in the old version. New: Microsoft.SecurityInsights/stable/2020-01-01/SecurityInsights.json#L1928:7 |
️️✔️
LintDiff [Detail]
️✔️
Validation passes for LintDiff.
️️✔️
Avocado [Detail]
️✔️
Validation passes for Avocado.
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-python - Release
|
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
|
azure-sdk-for-go - Release
|
azure-sdk-for-net - Release
|
Fixes schema generation failure:
|
Please add code owner to reviewer. |
Can one of the admins verify this patch? |
@alshulma can you please review this PR? the schema generation failed due to "alerts" property having different schemas: https://dev.azure.com/azure/azure-resource-manager-schemas/_build/results?buildId=11699&view=logs&j=ae501f3d-63ca-563e-a3d9-7c46870865a7&t=5b372c7a-4bf1-530e-6011-652a8f555b0d Line 1122. |
Follow the guideline... (however this is a fix on previously incorrect swagger) As identified in the automated checks there are breaking changes, Please follow Azure Breaking changes approval request form as defined @ Breaking Change Process |
@weidongxu-microsoft I confirmed with breakingchange tool owner. The tool doesn't support this case yet. It's not breaking change, since the schema doesn't change. |
@leni-msft Sure, you can let him do the merge after code owner is OK with it. The problem with that BreakingChange CI is that if it fails, I won't be able to press the merge button at all... |
code owner approves changes |
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
|
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
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.