Conversation
…-01-preview to version 2022-04-01
|
Hi, @imsiddhartha 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. vscswagger@microsoft.com |
Swagger Validation Report
|
| compared swaggers (via Oad v0.10.4)] | new version | base version |
|---|---|---|
| trafficmanager.json | 2022-04-01(530821c) | 2018-08-01(main) |
| trafficmanager.json | 2022-04-01(530821c) | 2022-04-01-preview(main) |
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 34 Warnings warning [Detail]
| compared tags (via openapi-validator v2.1.2) | new version | base version |
|---|---|---|
| package-2022-04 | package-2022-04(530821c) | default(main) |
[must fix]The following errors/warnings are introduced by current PR:
Only 30 items are listed, please refer to log for more details.
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
OperationsAPIImplementation |
Operations API must be implemented for 'Microsoft.Network'. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L1 |
PathForNestedResource |
The path for nested resource doest not meet the valid resource pattern. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L18 |
ResourceNameRestriction |
The resource name parameter 'profileName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L18 |
ResourceNameRestriction |
The resource name parameter 'endpointName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L18 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property name. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L59 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property type. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L59 |
DeleteResponseBodyEmpty |
The delete response body must be empty. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L312 |
GetCollectionOnlyHasValueAndNextLink |
Get endpoints for collections of resources must only have the value and nextLink properties in their model.Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L450 |
GetCollectionOnlyHasValueAndNextLink |
Get endpoints for collections of resources must only have the value and nextLink properties in their model.Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L489 |
ResourceNameRestriction |
The resource name parameter 'profileName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L507 |
DeleteResponseBodyEmpty |
The delete response body must be empty. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L659 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property name. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L696 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property type. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L696 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property location. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L696 |
GetCollectionOnlyHasValueAndNextLink |
Get endpoints for collections of resources must only have the value and nextLink properties in their model.Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L748 |
ResourceNameRestriction |
The resource name parameter 'profileName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L766 |
ParametersInPointGet |
Query parameter topLeft should be removed. Point Get's MUST not have query parameters other than api version. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L773 |
ParametersInPointGet |
Query parameter botRight should be removed. Point Get's MUST not have query parameters other than api version. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L773 |
PathForPutOperation |
The path for 'put' operation must be under a subscription and resource group. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L862 |
GetCollectionOnlyHasValueAndNextLink |
Get endpoints for collections of resources must only have the value and nextLink properties in their model.Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L880 |
PutResponseSchemaDescription |
Any Put MUST contain 200 and 201 return codes. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L911 |
DeleteOperationResponses |
The delete operation is defined without a 200 or 204 error response implementation,please add it.' Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L945 |
DeleteResponseBodyEmpty |
The delete response body must be empty. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L948 |
MissingTypeObject |
The schema 'DeleteOperationResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L968 |
MissingTypeObject |
The schema 'EndpointProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L979 |
XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L1054 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L1067 |
XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L1076 |
MissingTypeObject |
The schema 'HeatMapModel' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L1109 |
NestedResourcesMustHaveListOperation |
The nested resource 'HeatMapModel' does not have list operation, please add it. Location: Microsoft.Network/stable/2022-04-01/trafficmanager.json#L1109 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
️❌~[Staging] ServiceAPIReadinessTest: 0 Errors, 0 Warnings failed [Detail]
Tag package-2022-04; Prod region: Not deployed; Canary region: Not deployed
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️CadlAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️️✔️TypeSpec Validation succeeded [Detail] [Expand]
Validation passes for TypeSpec Validation.
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Swagger Generation Artifacts
|
Generated ApiView
|
|
Hi, @imsiddhartha your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
|
Hi @imsiddhartha, Your PR has some issues. Please fix the CI sequentially by following the order of
|
|
@imsiddhartha - Please fix the two linter errors introduced as part of this api-version change. https://github.com/Azure/azure-rest-api-specs/pull/22357/checks?check_run_id=11012171989 |
|
@akning-ms Fixed prettier checks |
|
The |
|
Hi @imsiddhartha, ping me for merge when your service is almost ready in production (like before about 1 weeks). according to API readiness check. Looks the new version is not deployed in production yet. |
|
Hi, @imsiddhartha. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
|
Hi, @imsiddhartha. The PR will be closed since the PR has no update for 28 days. If you still need the PR review to proceed, please reopen it and @ mention PR assignee. |
|
Reopening as we are ready to GET this released. |
|
Hi, @imsiddhartha. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
|
re-assign to Ray as seems I don't have merge permission anymore |
|
/azp run |
|
/azp run unifiedPipeline |
|
No pipelines are associated with this pull request. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM API Information (Control Plane)
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist (MS Employees Only):
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
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 you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.