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.

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

test snapshot- delete call portal api #29650

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

add change

3f796a7
Select commit
Loading
Failed to load commit list.
Draft

test snapshot- delete call portal api #29650

add change
3f796a7
Select commit
Loading
Failed to load commit list.
openapi-pipeline-app / Swagger LintDiff succeeded Jul 1, 2024 in 5m 22s

Swagger LintDiff succeeded

Details

Compared specs (v2.2.2) new version base version
package-2018-06 package-2018-06(3f796a7) package-2018-06(main)

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

Rule Message
OperationsApiResponseSchema The response schema of operations API '/providers/Microsoft.DataFactory/operations' does not match the ARM specification. Please standardize the schema.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L56
OperationsApiSchemaUsesCommonTypes Operations API path must follow the schema provided in the common types.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L57
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.DataFactory/stable/2018-06-01/datafactory.json#L313
PatchBodyParametersSchema Properties of a PATCH request body must not be required, property:type.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L398
GetResponseCodes GET operation must have response codes 200 and default. In addition, can have 202 if the GET represents the location header polling url.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L418
NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L457
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.DataFactory/stable/2018-06-01/datafactory.json#L657
GetResponseCodes GET operation must have response codes 200 and default. In addition, can have 202 if the GET represents the location header polling url.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L716
NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L758
ConsistentPatchProperties The property 'autoUpdate' in the request body either not apppear in the resource model or has the wrong level.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L801
ConsistentPatchProperties The property 'updateDelayOffset' in the request body either not apppear in the resource model or has the wrong level.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L801
XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L911
GetCollectionOnlyHasValueAndNextLink Get endpoints for collections of resources must only have the value and nextLink properties in their model.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L942
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1136
LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1142
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.DataFactory/stable/2018-06-01/datafactory.json#L1149
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1182
LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1188
OperationIdNounVerb Per the Noun_Verb convention for Operation Ids, the noun 'IntegrationRuntimes' 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.DataFactory/stable/2018-06-01/datafactory.json#L1379
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1465
LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1471
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.DataFactory/stable/2018-06-01/datafactory.json#L1774
GetResponseCodes GET operation must have response codes 200 and default. In addition, can have 202 if the GET represents the location header polling url.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1836
NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1878
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.DataFactory/stable/2018-06-01/datafactory.json#L1979
GetResponseCodes GET operation must have response codes 200 and default. In addition, can have 202 if the GET represents the location header polling url.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2041
NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2083
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.DataFactory/stable/2018-06-01/datafactory.json#L2184
GetResponseCodes GET operation must have response codes 200 and default. In addition, can have 202 if the GET represents the location header polling url.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2246
NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2288
ParametersInPost referencePipelineRunId is a query parameter. Post operation must not contain any query parameter other than api-version.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2355
ParametersInPost isRecovery is a query parameter. Post operation must not contain any query parameter other than api-version.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2355
ParametersInPost startActivityName is a query parameter. Post operation must not contain any query parameter other than api-version.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2355
ParametersInPost startFromFailure is a query parameter. Post operation must not contain any query parameter other than api-version.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2355
ParametersInPost isRecursive is a query parameter. Post operation must not contain any query parameter other than api-version.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2591
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.DataFactory/stable/2018-06-01/datafactory.json#L2725
GetResponseCodes GET operation must have response codes 200 and default. In addition, can have 202 if the GET represents the location header polling url.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2787
NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2829
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2921
LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2927
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L3015
LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L3021
PostResponseCodes Long-running POST operations must have responses with 202 and default return codes. They must also 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. They also must not have other response codes.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L3028
LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L3064
PostResponseCodes Long-running POST operations must have responses with 202 and default return codes. They must also 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. They also must not have other response codes.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L3071
LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L3107
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.DataFactory/stable/2018-06-01/datafactory.json#L3255
LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L3511
LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L3716
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.DataFactory/stable/2018-06-01/datafactory.json#L3768