-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Moved swagger specs from resources to solutions folder. #19826
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
Conversation
|
Hi, @vayada 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
|
| compared swaggers (via Oad v0.9.6)] | new version | base version |
|---|---|---|
| managedapplications.json | 2021-07-01(d295853) | 2021-07-01(main) |
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️❌LintDiff: 393 Errors, 19 Warnings failed [Detail]
The following errors/warnings are introduced by current PR:
Only 14 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
R3007 - PutGetPatchResponseSchema |
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Solutions/applications/{applicationName} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response. Location: Microsoft.Solutions/preview/2018-09-01-preview/managedapplications.json#L73 |
R3007 - PutGetPatchResponseSchema |
/{applicationId} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response. Location: Microsoft.Solutions/preview/2018-09-01-preview/managedapplications.json#L746 |
R3007 - PutGetPatchResponseSchema |
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Solutions/applications/{applicationName} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response. Location: Microsoft.Solutions/preview/2020-08-21-preview/managedapplications.json#L73 |
R3007 - PutGetPatchResponseSchema |
/{applicationId} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response. Location: Microsoft.Solutions/preview/2020-08-21-preview/managedapplications.json#L742 |
R3007 - PutGetPatchResponseSchema |
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Solutions/applications/{applicationName} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response. Location: Microsoft.Solutions/preview/2021-02-01-preview/managedapplications.json#L73 |
R3007 - PutGetPatchResponseSchema |
/{applicationId} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response. Location: Microsoft.Solutions/preview/2021-02-01-preview/managedapplications.json#L904 |
R3007 - PutGetPatchResponseSchema |
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Solutions/applications/{applicationName} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response. Location: Microsoft.Solutions/stable/2017-09-01/managedapplications.json#L73 |
R3007 - PutGetPatchResponseSchema |
/{applicationId} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response. Location: Microsoft.Solutions/stable/2017-09-01/managedapplications.json#L753 |
R3007 - PutGetPatchResponseSchema |
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Solutions/applications/{applicationName} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response. Location: Microsoft.Solutions/stable/2017-12-01/managedapplications.json#L73 |
R3007 - PutGetPatchResponseSchema |
/{applicationId} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response. Location: Microsoft.Solutions/stable/2017-12-01/managedapplications.json#L746 |
R3007 - PutGetPatchResponseSchema |
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Solutions/applications/{applicationName} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response. Location: Microsoft.Solutions/stable/2018-02-01/managedapplications.json#L73 |
R3007 - PutGetPatchResponseSchema |
/{applicationId} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response. Location: Microsoft.Solutions/stable/2018-02-01/managedapplications.json#L746 |
R3007 - PutGetPatchResponseSchema |
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Solutions/applications/{applicationName} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response. Location: Microsoft.Solutions/stable/2018-03-01/managedapplications.json#L73 |
R3007 - PutGetPatchResponseSchema |
/{applicationId} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response. Location: Microsoft.Solutions/stable/2018-03-01/managedapplications.json#L746 |
The following errors/warnings exist before current PR submission:
Only 14 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
| Since operation 'ListOperations' response has model definition 'x-ms-pageable', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.Solutions/preview/2018-09-01-preview/managedapplications.json#L42 |
|
| Since operation 'ListOperations' response has model definition 'x-ms-pageable', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.Solutions/preview/2020-08-21-preview/managedapplications.json#L42 |
|
| Since operation 'ListOperations' response has model definition 'x-ms-pageable', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.Solutions/preview/2021-02-01-preview/managedapplications.json#L42 |
|
| Since operation 'ListOperations' response has model definition 'x-ms-pageable', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.Solutions/stable/2017-09-01/managedapplications.json#L42 |
|
| Since operation 'ListOperations' response has model definition 'x-ms-pageable', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.Solutions/stable/2017-12-01/managedapplications.json#L42 |
|
| Since operation 'ListOperations' response has model definition 'x-ms-pageable', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.Solutions/stable/2018-02-01/managedapplications.json#L42 |
|
| Since operation 'ListOperations' response has model definition 'x-ms-pageable', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.Solutions/stable/2018-03-01/managedapplications.json#L42 |
|
| Since operation 'ListOperations' response has model definition 'x-ms-pageable', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.Solutions/stable/2018-06-01/managedapplications.json#L42 |
|
| Since operation 'ListOperations' response has model definition 'x-ms-pageable', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.Solutions/stable/2019-07-01/managedapplications.json#L42 |
|
| Since operation 'ListOperations' response has model definition 'x-ms-pageable', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.Solutions/stable/2021-07-01/managedapplications.json#L42 |
|
| The operation 'Applications_Update' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. Location: Microsoft.Solutions/preview/2020-08-21-preview/managedapplications.json#L263 |
|
| Based on the response model schema, operation 'jitRequests_ListBySubscription' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Solutions/preview/2018-09-01-preview/managedapplications.json#L1191 |
|
| Based on the response model schema, operation 'jitRequests_ListByResourceGroup' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Solutions/preview/2018-09-01-preview/managedapplications.json#L1227 |
|
| Based on the response model schema, operation 'jitRequests_ListBySubscription' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Solutions/preview/2020-08-21-preview/managedapplications.json#L1187 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️ApiReadinessCheck 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.
️❌SDK Track2 Validation: 23 Errors, 2 Warnings failed [Detail]
- The following tags are being changed in this PR
- "https://github.com/Azure/azure-rest-api-specs/blob/d2958531ae3128a7aa789161a1b4e67ded6e0541/specification/solutions/resource-manager/readme.md#tag-package-managedapplications-2021-07">solutions/resource-manager/readme.md#package-managedapplications-2021-07
- "https://github.com/Azure/azure-rest-api-specs/blob/d2958531ae3128a7aa789161a1b4e67ded6e0541/specification/solutions/resource-manager/readme.md#tag-package-managedapplications-2021-02">solutions/resource-manager/readme.md#package-managedapplications-2021-02
- "https://github.com/Azure/azure-rest-api-specs/blob/d2958531ae3128a7aa789161a1b4e67ded6e0541/specification/solutions/resource-manager/readme.md#tag-package-managedapplications-2020-08">solutions/resource-manager/readme.md#package-managedapplications-2020-08
- "https://github.com/Azure/azure-rest-api-specs/blob/d2958531ae3128a7aa789161a1b4e67ded6e0541/specification/solutions/resource-manager/readme.md#tag-package-managedapplications-2019-07">solutions/resource-manager/readme.md#package-managedapplications-2019-07
- "https://github.com/Azure/azure-rest-api-specs/blob/d2958531ae3128a7aa789161a1b4e67ded6e0541/specification/solutions/resource-manager/readme.md#tag-package-managedapplications-2018-09">solutions/resource-manager/readme.md#package-managedapplications-2018-09
- "https://github.com/Azure/azure-rest-api-specs/blob/d2958531ae3128a7aa789161a1b4e67ded6e0541/specification/solutions/resource-manager/readme.md#tag-package-managedapplications-2018-06">solutions/resource-manager/readme.md#package-managedapplications-2018-06
- "https://github.com/Azure/azure-rest-api-specs/blob/d2958531ae3128a7aa789161a1b4e67ded6e0541/specification/solutions/resource-manager/readme.md#tag-package-managedapplications-2018-03">solutions/resource-manager/readme.md#package-managedapplications-2018-03
- "https://github.com/Azure/azure-rest-api-specs/blob/d2958531ae3128a7aa789161a1b4e67ded6e0541/specification/solutions/resource-manager/readme.md#tag-package-managedapplications-2018-02">solutions/resource-manager/readme.md#package-managedapplications-2018-02
- "https://github.com/Azure/azure-rest-api-specs/blob/d2958531ae3128a7aa789161a1b4e67ded6e0541/specification/solutions/resource-manager/readme.md#tag-package-managedapplications-2017-12">solutions/resource-manager/readme.md#package-managedapplications-2017-12
- "https://github.com/Azure/azure-rest-api-specs/blob/d2958531ae3128a7aa789161a1b4e67ded6e0541/specification/solutions/resource-manager/readme.md#tag-package-managedapplications-2017-09">solutions/resource-manager/readme.md#package-managedapplications-2017-09
Only 14 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
PreCheck/DuplicateSchema |
"readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2021-02", "details":"Duplicate Schema named 'Operation' (10 differences):\n - properties.name.$ref: "#/components/schemas/schemas:141" => "#/components/schemas/schemas:243"\n - properties.name.description: "Operation name: provider/resource/operation" => "The name of the operation, as per Resource-Based Access Control (RBAC). Examples: \"Microsoft.Compute/virtualMachines/write\", \"Microsoft.Compute/virtualMachines/capture/action\""\n - properties.name.readOnly: => true\n - properties.isDataAction.description: "Indicates whether the operation is a data action" => "Whether the operation applies to data-plane. This is \"true\" for data-plane operations and \"false\" for ARM/control-plane operations."\n - properties.isDataAction.readOnly: => true\n - properties.display.$ref: "#/components/schemas/schemas:142" => "#/components/schemas/schemas:244"\n - properties.display.description: "The object that represents the operation." => "Localized display information for this particular operation."\n - properties.origin: => "x-ms-enum":"name":"Origin", "modelAsString":true, "$ref":"#/components/schemas/Origin", "description":"The intended executor of the operation; as in Resource Based Access Control (RBAC) and audit logs UX. Default value is \"user, system\"", "readOnly":true\n - properties.actionType: => "x-ms-enum":"name":"ActionType", "modelAsString":true, "$ref":"#/components/schemas/ActionType", "description":"Enum. Indicates the action type. \"Internal\" refers to actions that are for internal only APIs.", "readOnly":true\n - title: => "REST API Operation"; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
PreCheck/DuplicateSchema |
"readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2021-02", "details":"Duplicate Schema named 'Operation-display' (10 differences):\n - properties.provider.$ref: "#/components/schemas/schemas:143" => "#/components/schemas/schemas:245"\n - properties.provider.description: "Service provider: Microsoft.Solutions" => "The localized friendly form of the resource provider name, e.g. \"Microsoft Monitoring Insights\" or \"Microsoft Compute\"."\n - properties.provider.readOnly: => true\n - properties.resource.$ref: "#/components/schemas/schemas:144" => "#/components/schemas/schemas:246"\n - properties.resource.description: "Resource on which the operation is performed: Application, JitRequest, etc." => "The localized friendly name of the resource type related to this operation. E.g. \"Virtual Machines\" or \"Job Schedule Collections\"."\n - properties.resource.readOnly: => true\n - properties.operation.$ref: "#/components/schemas/schemas:145" => "#/components/schemas/schemas:247"\n - properties.operation.description: "Operation type: Read, write, delete, etc." => "The concise, localized friendly name for the operation; suitable for dropdowns. E.g. \"Create or Update Virtual Machine\", \"Restart Virtual Machine\"."\n - properties.operation.readOnly: => true\n - properties.description.description: "Localized friendly description for the operation" => "The short, localized friendly description of the operation; suitable for tool tips and detailed views."; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
PreCheck/DuplicateSchema |
"readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2021-02", "details":"Duplicate Schema named 'OperationListResult' (7 differences):\n - properties.value.$ref: "#/components/schemas/schemas:148" => "#/components/schemas/schemas:252"\n - properties.value.description: "List of Microsoft.Solutions operations." => "List of operations supported by the resource provider"\n - properties.value.x-ms-identifiers: => ["name"]\n - properties.value.readOnly: => true\n - properties.nextLink.$ref: "#/components/schemas/schemas:149" => "#/components/schemas/schemas:253"\n - properties.nextLink.description: "URL to get the next set of operation list results if there are any." => "URL to get the next set of operation list results (if there are any)."\n - properties.nextLink.readOnly: => true; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
|
"readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2021-02", "details":"Error: 3 errors occured -- cannot continue." |
PreCheck/DuplicateSchema |
"readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2020-08", "details":"Duplicate Schema named 'Operation' (10 differences):\n - properties.name.$ref: "#/components/schemas/schemas:141" => "#/components/schemas/schemas:272"\n - properties.name.description: "Operation name: provider/resource/operation" => "The name of the operation, as per Resource-Based Access Control (RBAC). Examples: \"Microsoft.Compute/virtualMachines/write\", \"Microsoft.Compute/virtualMachines/capture/action\""\n - properties.name.readOnly: => true\n - properties.isDataAction.description: "Indicates whether the operation is a data action" => "Whether the operation applies to data-plane. This is \"true\" for data-plane operations and \"false\" for ARM/control-plane operations."\n - properties.isDataAction.readOnly: => true\n - properties.display.$ref: "#/components/schemas/schemas:142" => "#/components/schemas/schemas:273"\n - properties.display.description: "The object that represents the operation." => "Localized display information for this particular operation."\n - properties.origin: => "x-ms-enum":"name":"Origin", "modelAsString":true, "$ref":"#/components/schemas/Origin", "description":"The intended executor of the operation; as in Resource Based Access Control (RBAC) and audit logs UX. Default value is \"user, system\"", "readOnly":true\n - properties.actionType: => "x-ms-enum":"name":"ActionType", "modelAsString":true, "$ref":"#/components/schemas/ActionType", "description":"Enum. Indicates the action type. \"Internal\" refers to actions that are for internal only APIs.", "readOnly":true\n - title: => "REST API Operation"; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
PreCheck/DuplicateSchema |
"readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2020-08", "details":"Duplicate Schema named 'Operation-display' (10 differences):\n - properties.provider.$ref: "#/components/schemas/schemas:143" => "#/components/schemas/schemas:274"\n - properties.provider.description: "Service provider: Microsoft.Solutions" => "The localized friendly form of the resource provider name, e.g. \"Microsoft Monitoring Insights\" or \"Microsoft Compute\"."\n - properties.provider.readOnly: => true\n - properties.resource.$ref: "#/components/schemas/schemas:144" => "#/components/schemas/schemas:275"\n - properties.resource.description: "Resource on which the operation is performed: Application, JitRequest, etc." => "The localized friendly name of the resource type related to this operation. E.g. \"Virtual Machines\" or \"Job Schedule Collections\"."\n - properties.resource.readOnly: => true\n - properties.operation.$ref: "#/components/schemas/schemas:145" => "#/components/schemas/schemas:276"\n - properties.operation.description: "Operation type: Read, write, delete, etc." => "The concise, localized friendly name for the operation; suitable for dropdowns. E.g. \"Create or Update Virtual Machine\", \"Restart Virtual Machine\"."\n - properties.operation.readOnly: => true\n - properties.description.description: "Localized friendly description for the operation" => "The short, localized friendly description of the operation; suitable for tool tips and detailed views."; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
PreCheck/DuplicateSchema |
"readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2020-08", "details":"Duplicate Schema named 'OperationListResult' (7 differences):\n - properties.value.$ref: "#/components/schemas/schemas:148" => "#/components/schemas/schemas:281"\n - properties.value.description: "List of Microsoft.Solutions operations." => "List of operations supported by the resource provider"\n - properties.value.x-ms-identifiers: => ["name"]\n - properties.value.readOnly: => true\n - properties.nextLink.$ref: "#/components/schemas/schemas:149" => "#/components/schemas/schemas:282"\n - properties.nextLink.description: "URL to get the next set of operation list results if there are any." => "URL to get the next set of operation list results (if there are any)."\n - properties.nextLink.readOnly: => true; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
|
"readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2020-08", "details":"Error: 3 errors occured -- cannot continue." |
PreCheck/DuplicateSchema |
"readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2019-07", "details":"Duplicate Schema named 'Operation' (9 differences):\n - properties.name.$ref: "#/components/schemas/schemas:141" => "#/components/schemas/schemas:268"\n - properties.name.description: "Operation name: provider/resource/operation" => "The name of the operation, as per Resource-Based Access Control (RBAC). Examples: \"Microsoft.Compute/virtualMachines/write\", \"Microsoft.Compute/virtualMachines/capture/action\""\n - properties.name.readOnly: => true\n - properties.display.$ref: "#/components/schemas/schemas:142" => "#/components/schemas/schemas:269"\n - properties.display.description: "The object that represents the operation." => "Localized display information for this particular operation."\n - properties.isDataAction: => "description":"Whether the operation applies to data-plane. This is \"true\" for data-plane operations and \"false\" for ARM/control-plane operations.", "type":"boolean", "readOnly":true\n - properties.origin: => "x-ms-enum":"name":"Origin", "modelAsString":true, "$ref":"#/components/schemas/Origin", "description":"The intended executor of the operation; as in Resource Based Access Control (RBAC) and audit logs UX. Default value is \"user, system\"", "readOnly":true\n - properties.actionType: => "x-ms-enum":"name":"ActionType", "modelAsString":true, "$ref":"#/components/schemas/ActionType", "description":"Enum. Indicates the action type. \"Internal\" refers to actions that are for internal only APIs.", "readOnly":true\n - title: => "REST API Operation"; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
PreCheck/DuplicateSchema |
"readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2019-07", "details":"Duplicate Schema named 'Operation-display' (10 differences):\n - properties.provider.$ref: "#/components/schemas/schemas:143" => "#/components/schemas/schemas:270"\n - properties.provider.description: "Service provider: Microsoft.Solutions" => "The localized friendly form of the resource provider name, e.g. \"Microsoft Monitoring Insights\" or \"Microsoft Compute\"."\n - properties.provider.readOnly: => true\n - properties.resource.$ref: "#/components/schemas/schemas:144" => "#/components/schemas/schemas:271"\n - properties.resource.description: "Resource on which the operation is performed: Application, JitRequest, etc." => "The localized friendly name of the resource type related to this operation. E.g. \"Virtual Machines\" or \"Job Schedule Collections\"."\n - properties.resource.readOnly: => true\n - properties.operation.$ref: "#/components/schemas/schemas:145" => "#/components/schemas/schemas:272"\n - properties.operation.description: "Operation type: Read, write, delete, etc." => "The concise, localized friendly name for the operation; suitable for dropdowns. E.g. \"Create or Update Virtual Machine\", \"Restart Virtual Machine\"."\n - properties.operation.readOnly: => true\n - properties.description: => "$ref":"#/components/schemas/schemas:273", "description":"The short, localized friendly description of the operation; suitable for tool tips and detailed views.", "readOnly":true; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
|
"readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2019-07", "details":"Error: 2 errors occured -- cannot continue." |
PreCheck/DuplicateSchema |
"readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2018-09", "details":"Duplicate Schema named 'Operation' (9 differences):\n - properties.name.$ref: "#/components/schemas/schemas:129" => "#/components/schemas/schemas:251"\n - properties.name.description: "Operation name: provider/resource/operation" => "The name of the operation, as per Resource-Based Access Control (RBAC). Examples: \"Microsoft.Compute/virtualMachines/write\", \"Microsoft.Compute/virtualMachines/capture/action\""\n - properties.name.readOnly: => true\n - properties.display.$ref: "#/components/schemas/schemas:130" => "#/components/schemas/schemas:252"\n - properties.display.description: "The object that represents the operation." => "Localized display information for this particular operation."\n - properties.isDataAction: => "description":"Whether the operation applies to data-plane. This is \"true\" for data-plane operations and \"false\" for ARM/control-plane operations.", "type":"boolean", "readOnly":true\n - properties.origin: => "x-ms-enum":"name":"Origin", "modelAsString":true, "$ref":"#/components/schemas/Origin", "description":"The intended executor of the operation; as in Resource Based Access Control (RBAC) and audit logs UX. Default value is \"user, system\"", "readOnly":true\n - properties.actionType: => "x-ms-enum":"name":"ActionType", "modelAsString":true, "$ref":"#/components/schemas/ActionType", "description":"Enum. Indicates the action type. \"Internal\" refers to actions that are for internal only APIs.", "readOnly":true\n - title: => "REST API Operation"; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
PreCheck/DuplicateSchema |
"readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2018-09", "details":"Duplicate Schema named 'Operation-display' (10 differences):\n - properties.provider.$ref: "#/components/schemas/schemas:131" => "#/components/schemas/schemas:253"\n - properties.provider.description: "Service provider: Microsoft.Solutions" => "The localized friendly form of the resource provider name, e.g. \"Microsoft Monitoring Insights\" or \"Microsoft Compute\"."\n - properties.provider.readOnly: => true\n - properties.resource.$ref: "#/components/schemas/schemas:132" => "#/components/schemas/schemas:254"\n - properties.resource.description: "Resource on which the operation is performed: Application, JitRequest, etc." => "The localized friendly name of the resource type related to this operation. E.g. \"Virtual Machines\" or \"Job Schedule Collections\"."\n - properties.resource.readOnly: => true\n - properties.operation.$ref: "#/components/schemas/schemas:133" => "#/components/schemas/schemas:255"\n - properties.operation.description: "Operation type: Read, write, delete, etc." => "The concise, localized friendly name for the operation; suitable for dropdowns. E.g. \"Create or Update Virtual Machine\", \"Restart Virtual Machine\"."\n - properties.operation.readOnly: => true\n - properties.description: => "$ref":"#/components/schemas/schemas:256", "description":"The short, localized friendly description of the operation; suitable for tool tips and detailed views.", "readOnly":true; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
|
"readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2018-09", "details":"Error: 2 errors occured -- cannot continue." |
The following errors/warnings exist before current PR submission:
| Rule | Message |
|---|---|
| "readme":"solutions/resource-manager/readme.md", "tag":"package-managedapplications-2021-07", "details":"Security scheme azure_auth is unknown and will not be processed. Only supported types are AADToken, AzureKey, Anonymous" |
️️✔️PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️❌Lint(RPaaS): 3 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
R4023 - Rpaas_CreateOperationAsyncResponseValidation |
[RPaaS] An async PUT operation must set ''x-ms-long-running-operation' : true''. Location: Microsoft.Solutions/stable/2021-07-01/managedapplications.json#L368 |
R4023 - Rpaas_CreateOperationAsyncResponseValidation |
[RPaaS] An async PUT operation must set long running operation options 'x-ms-long-running-operation-options' Location: Microsoft.Solutions/stable/2021-07-01/managedapplications.json#L368 |
R4031 - Rpaas_ResourceProvisioningState |
[RPaaS] The resource ApplicationDefinition is defined without 'provisioningState' in properties bag, consider adding the provisioningState for it. Location: Microsoft.Solutions/stable/2021-07-01/managedapplications.json#L1614 |
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
Swagger Generation Artifacts
|
|
Hi @vayada, Your PR has some issues. Please fix the CI sequentially by following the order of
|
|
@ruowan This PR is just moving swagger from resources folder to solutions folder as per Josephine's suggestion. There is not other change except moving specs from one location to another as per Josephine's suggestion. So, please help in merging this PR. Source folders: Target Folder: |
|
There are some validation errors, could you take a look and fix them? |
|
NewApiVersionRequired reason: |
|
Hi @vayada, 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. |
@ruowan Fixed all validation errors and currently in touch with ARM API reviewer & breaking change reviewer. Can you look at sdk errors and let me know what needs to be done for that. Not sure what's causing duplicate key error as below. "location":"specification/solutions/resource-manager/readme.md", |
|
@ruowan I have fixed all the validation errors. I have already got the Breaking Change approval. Can you check it now. |
|
Hi, @jianyexi Could you take a look at lintDiff, why there are so many lintDiff error? |
|
@vayada the restructure causes the lintDiff failure, could you confirm all the versions except 2021-07-01 are coming from the old folder or branch and without any Api changes? |
|
| ### Tag: package-managedapplications-2021-02 | ||
|
|
||
| These settings apply only when `--tag=package-managedapplications-2021-02` is specified on the command line. | ||
|
|
||
| ``` yaml $(tag) == 'package-managedapplications-2021-02' | ||
| input-file: | ||
| - Microsoft.Solutions/preview/2021-02-01-preview/managedapplications.json | ||
| ``` |
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.
tag name shall contain preview since it only contain files under preview folder
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for 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
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following appy 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.
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
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 any of the following scenarios apply to the PR, request approval from the Breaking Change 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.