Skip to content
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.

Sign up for GitHub

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] Publish private branch 'gachauhan-iprangenew' #27329

Merged
merged 8 commits into from
Jan 19, 2024

Fixed prettier check

7c0d33f
Select commit
Loading
Failed to load commit list.
Merged

[Hub Generated] Publish private branch 'gachauhan-iprangenew' #27329

Fixed prettier check
7c0d33f
Select commit
Loading
Failed to load commit list.
openapi-pipeline-app / Swagger LintDiff succeeded Jan 10, 2024 in 2m 56s

Swagger LintDiff succeeded

LintDiff
View Azure DevOps build log for more details.

Details

compared tags (via openapi-validator v2.1.6) new version base version
package-2023-12-01 package-2023-12-01(7c0d33f) default(main)

The following errors/warnings exist before current PR submission:
Only 50 items are listed, please refer to log for more details.

Rule Message
❌ OperationsApiSchemaUsesCommonTypes Operations API path must follow the schema provided in the common types.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L34
❌ ResourceNameRestriction The resource name parameter 'deviceName' should be defined with a 'pattern' restriction.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L188
❌ ParametersOrder The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L189
❌ ParametersOrder The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L236
❌ PutResponseCodes Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L236
❌ DeleteResponseCodes Long-running delete operations must have responses with 202, 204 and default return codes. They also must have no other response codes.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L292
❌ ParametersOrder The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L292
❌ LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L320
❌ LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L329
❌ ParametersOrder The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L340
❌ ResourceNameRestriction The resource name parameter 'deviceName' should be defined with a 'pattern' restriction.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L394
❌ ParametersOrder The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L395
❌ ResourceNameRestriction The resource name parameter 'deviceName' should be defined with a 'pattern' restriction.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L443
❌ ParametersOrder The parameters:deviceName,name,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L444
❌ ResourceNameRestriction The resource name parameter 'deviceName' should be defined with a 'pattern' restriction.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L496
❌ ParametersOrder The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L497
❌ ResourceNameRestriction The resource name parameter 'deviceName' should be defined with a 'pattern' restriction.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L545
❌ ParametersOrder The parameters:deviceName,name,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L546
❌ ParametersOrder The parameters:deviceName,name,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L597
❌ ProvisioningStateSpecifiedForLROPut 200 response schema in long running PUT operation is missing ProvisioningState property. A LRO PUT operations response schema must have ProvisioningState specified for the 200 and 201 status codes.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L597
❌ ProvisioningStateSpecifiedForLROPut 201 response schema in long running PUT operation is missing ProvisioningState property. A LRO PUT operations response schema must have ProvisioningState specified for the 200 and 201 status codes.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L597
❌ PutResponseCodes Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L597
❌ LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L644
❌ LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L650
❌ DeleteResponseCodes Long-running delete operations must have responses with 202, 204 and default return codes. They also must have no other response codes.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L661
❌ ParametersOrder The parameters:deviceName,name,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L661
❌ LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L696
❌ LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L705
❌ ResourceNameRestriction The resource name parameter 'deviceName' should be defined with a 'pattern' restriction.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L717
❌ PostResponseCodes 200 return code does not have a schema specified. LRO POST must have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L718
❌ ParametersInPost capacityName is a query parameter. Post operation must not contain any query parameter other than api-version.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L724
❌ LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L759
❌ LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L768
❌ ResourceNameRestriction The resource name parameter 'deviceName' should be defined with a 'pattern' restriction.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L783
❌ XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L784
❌ OperationIdNounVerb Per the Noun_Verb convention for Operation Ids, the noun 'DeviceCapacityInfo' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L789
❌ EvenSegmentedPathForPutOperation API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments).
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L829
❌ ResourceNameRestriction The resource name parameter 'deviceName' should be defined with a 'pattern' restriction.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L829
❌ ParametersOrder The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L830
❌ XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L830
❌ ParametersOrder The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L874
❌ ProvisioningStateSpecifiedForLROPut 200 response schema in long running PUT operation is missing ProvisioningState property. A LRO PUT operations response schema must have ProvisioningState specified for the 200 and 201 status codes.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L874
❌ ProvisioningStateSpecifiedForLROPut 201 response schema in long running PUT operation is missing ProvisioningState property. A LRO PUT operations response schema must have ProvisioningState specified for the 200 and 201 status codes.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L874
❌ PutResponseCodes Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L874
❌ LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L914
❌ LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L920
❌ EvenSegmentedPathForPutOperation API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments).
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L932
❌ ResourceNameRestriction The resource name parameter 'deviceName' should be defined with a 'pattern' restriction.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L932
❌ ParametersOrder The parameters:deviceName,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L933
❌ XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
Location: Microsoft.DataBoxEdge/stable/2023-12-01/databoxedge.json#L933
View more details on openapi-pipeline-app