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

[suppression test] data factory #3256

Closed
wants to merge 15 commits into from

Merge branch 'main' into jacktn/bug-suppressions

34317ed
Select commit
Loading
Failed to load commit list.
Closed

[suppression test] data factory #3256

Merge branch 'main' into jacktn/bug-suppressions
34317ed
Select commit
Loading
Failed to load commit list.
openapi-pipeline-app-test / Swagger LintDiff failed Apr 24, 2024 in 4m 13s

Swagger LintDiff failed

LintDiff: 69 Errors, 44 Warnings
View Azure DevOps build log for more details.

Details

[must fix]The following errors/warnings are introduced by current PR:

Rule Message Related RPC [For API reviewers]
OperationsAPIImplementation Operations API must be implemented for 'Microsoft.DataFactory'.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1
AutoRest exception "tag":"package-2022-05-01",
"details":"[OperationAbortedException] Error occurred. Exiting."
AutoRest exception "tag":"package-2022-05-01",
"details":"!Error: [OperationAbortedException] Error occurred. Exiting."
AutoRest exception "tag":"package-2022-05-01",
"details":"Autorest completed with an error. If you think the error message is unclear,
or is a bug,
please declare an issues at https://github.com/Azure/autorest/issues with the error message you are seeing."
AutoRest exception "tag":"package-2022-05-01",
"details":"Syntax Error Encountered: Syntax error: can not read a block mapping entry; a multiline key may not be an implicit key"


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

Rule Message
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#L316
PatchBodyParametersSchema Properties of a PATCH request body must not be required, property:type.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L401
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#L421
NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L460
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#L660
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#L719
NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L761
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#L804
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#L804
XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L914
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#L945
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1139
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#L1145
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#L1152
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1185
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#L1191
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#L1382
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1468
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#L1474
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#L1777
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#L1839
NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L1881
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#L1982
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#L2044
NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2086
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#L2187
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#L2249
NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2291
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#L2358
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#L2358
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#L2358
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#L2358
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#L2594
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#L2728
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#L2790
NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2832
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L2924
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#L2930
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.DataFactory/stable/2018-06-01/datafactory.json#L3018
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#L3024
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#L3031
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#L3067
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#L3074
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#L3110
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#L3258
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#L3514
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#L3719
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#L3771
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#L3975
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#L4034