-
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
[Hub Generated] Review request for Microsoft.AlertsManagement to add version preview/2021-01-01-preview #12748
[Hub Generated] Review request for Microsoft.AlertsManagement to add version preview/2021-01-01-preview #12748
Conversation
…w/2020-08-04-preview to version 2021-01-01-preview
Hi, @dishonono 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] |
Swagger Validation Report
|
Rule | Message |
---|---|
OperationId should contain the verb: 'migratefromsmartdetection' in:'MigrateFromSmartDetection_StartMigration'. Consider updating the operationId Location: Microsoft.AlertsManagement/preview/2021-01-01-preview/MigrateFromSmartDetections.json#L36 |
️⚠️
Avocado: 1 Warnings warning [Detail]
Rule | Message |
---|---|
The default tag contains multiple API versions swaggers. readme: specification/alertsmanagement/resource-manager/readme.md tag: specification/alertsmanagement/resource-manager/readme.md#tag-package-2019-06-preview |
️️✔️
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.
- Compared Swaggers (Based on Oad v0.8.6)
️⚠️
[Staging] Cross Version BreakingChange (Base on stable version): 35 Warnings warning [Detail]
Only 10 items are listed, please refer to log for more details.
- Compared Swaggers (Based on Oad v0.8.6)
- original: stable/2019-03-01/AlertsManagement.json <---> new: preview/2021-01-01-preview/AlertsManagement.json
Rule | Message |
---|---|
The new version is missing a path that was found in the old version. Was path '/providers/Microsoft.AlertsManagement/alertsMetaData' removed or restructured? Old: Microsoft.AlertsManagement/stable/2019-03-01/AlertsManagement.json#L55:5 |
|
The new version is missing a path that was found in the old version. Was path '/{scope}/providers/Microsoft.AlertsManagement/alerts' removed or restructured? Old: Microsoft.AlertsManagement/stable/2019-03-01/AlertsManagement.json#L91:5 |
|
The new version is missing a path that was found in the old version. Was path '/{scope}/providers/Microsoft.AlertsManagement/alerts/{alertId}' removed or restructured? Old: Microsoft.AlertsManagement/stable/2019-03-01/AlertsManagement.json#L181:5 |
|
The new version is missing a path that was found in the old version. Was path '/{scope}/providers/Microsoft.AlertsManagement/alerts/{alertId}/changestate' removed or restructured? Old: Microsoft.AlertsManagement/stable/2019-03-01/AlertsManagement.json#L221:5 |
|
The new version is missing a path that was found in the old version. Was path '/{scope}/providers/Microsoft.AlertsManagement/alerts/{alertId}/history' removed or restructured? Old: Microsoft.AlertsManagement/stable/2019-03-01/AlertsManagement.json#L260:5 |
|
The new version is missing a path that was found in the old version. Was path '/{scope}/providers/Microsoft.AlertsManagement/alertsSummary' removed or restructured? Old: Microsoft.AlertsManagement/stable/2019-03-01/AlertsManagement.json#L296:5 |
|
The new version is missing a client parameter that was found in the old version. Was 'scope' removed or renamed? New: Microsoft.AlertsManagement/preview/2021-01-01-preview/AlertsManagement.json#L108:3 Old: Microsoft.AlertsManagement/stable/2019-03-01/AlertsManagement.json#L366:3 |
|
The new version is missing a client parameter that was found in the old version. Was 'subscriptionId' removed or renamed? New: Microsoft.AlertsManagement/preview/2021-01-01-preview/AlertsManagement.json#L108:3 Old: Microsoft.AlertsManagement/stable/2019-03-01/AlertsManagement.json#L366:3 |
|
The new version is missing a client parameter that was found in the old version. Was 'api-version' removed or renamed? New: Microsoft.AlertsManagement/preview/2021-01-01-preview/AlertsManagement.json#L108:3 Old: Microsoft.AlertsManagement/stable/2019-03-01/AlertsManagement.json#L366:3 |
|
The new version is missing a client parameter that was found in the old version. Was 'alertId' removed or renamed? New: Microsoft.AlertsManagement/preview/2021-01-01-preview/AlertsManagement.json#L108:3 Old: Microsoft.AlertsManagement/stable/2019-03-01/AlertsManagement.json#L366:3 |
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️
[Staging] SDK Track2 Validation: 5 Warnings warning [Detail]
- The following tags are being changed in this PR
Rule | Message |
---|---|
"readme":"alertsmanagement/resource-manager/readme.md", "tag":"package-preview-2021-01", "details":"The schema 'operation' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"alertsmanagement/resource-manager/readme.md", "tag":"package-preview-2021-01", "details":"The schema 'operationsList' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"alertsmanagement/resource-manager/readme.md", "tag":"package-preview-2021-01", "details":"The schema 'SmartDetectionMigrationRequest' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"alertsmanagement/resource-manager/readme.md", "tag":"package-preview-2021-01", "details":"The schema 'MigrationStatusResponseProperties' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
"readme":"alertsmanagement/resource-manager/readme.md", "tag":"package-preview-2021-01", "details":"Checking for duplicate schemas, this could take a (long) while. Run with --verbose for more detail." |
️️✔️
[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
Swagger Generation Artifacts
|
Hi, @dishonono your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board([email protected]). cc @ |
this is the ARM manifest PR: |
...anager/Microsoft.AlertsManagement/preview/2021-01-01-preview/MigrateFromSmartDetections.json
Show resolved
Hide resolved
...anager/Microsoft.AlertsManagement/preview/2021-01-01-preview/MigrateFromSmartDetections.json
Outdated
Show resolved
Hide resolved
...sManagement/preview/2021-01-01-preview/examples/migrateFromSmartDetectionStartMigration.json
Outdated
Show resolved
Hide resolved
...anager/Microsoft.AlertsManagement/preview/2021-01-01-preview/MigrateFromSmartDetections.json
Outdated
Show resolved
Hide resolved
...anager/Microsoft.AlertsManagement/preview/2021-01-01-preview/MigrateFromSmartDetections.json
Show resolved
Hide resolved
...anager/Microsoft.AlertsManagement/preview/2021-01-01-preview/MigrateFromSmartDetections.json
Outdated
Show resolved
Hide resolved
Hi @jorgecotillo , |
...anager/Microsoft.AlertsManagement/preview/2021-01-01-preview/MigrateFromSmartDetections.json
Show resolved
Hide resolved
...anager/Microsoft.AlertsManagement/preview/2021-01-01-preview/MigrateFromSmartDetections.json
Outdated
Show resolved
Hide resolved
...anager/Microsoft.AlertsManagement/preview/2021-01-01-preview/MigrateFromSmartDetections.json
Outdated
Show resolved
Hide resolved
@dishonono take a look at my GET and POST comment from 2/10 |
/azp run unifiedPipeline |
No pipelines are associated with this pull request. |
/azp run unifiedPipeline |
No pipelines are associated with this pull request. |
@@ -44,6 +44,16 @@ openapi-type: arm | |||
tag: package-2019-06-preview |
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.
Will you use new api version for your SDK release? if yes, we should change tag to your new tag for 2021-01 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.
Hi,
no . We don't want to use the new API version for the SDK release
…version preview/2021-01-01-preview (Azure#12748) * Adds base for updating Microsoft.AlertsManagement from version preview/2020-08-04-preview to version 2021-01-01-preview * Updates readme * Updates API version in new specs and examples * first commit * fix: "Client Api Version." * try add x-ms-long-running-operation-options * some renames * try to remove long operation * fixes from code review * fix typo * code review fixes * try fix lintdiff * remove the GET from the swagger , Add 200 to the POST * fix spelling * remove location header from the 200 response
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
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.