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

Add updatemachinekey api #29730

Merged
merged 7 commits into from
Jul 31, 2024
+62 −1

Change post address to conform to arm

2f0974e
Select commit
Loading
Failed to load commit list.
Merged

Add updatemachinekey api #29730

Change post address to conform to arm
2f0974e
Select commit
Loading
Failed to load commit list.
openapi-pipeline-app / Swagger LintDiff succeeded Jul 24, 2024 in 5m 59s

Swagger LintDiff succeeded

LintDiff
View Azure DevOps build log for more details.

Details

Compared specs (v2.2.3) new version base version
package-2024-04 package-2024-04(2f0974e) package-2024-04(release-web-2024-04-01)

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

Rule Message
❌ 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.Web/stable/2024-04-01/WebApps.json#L108
❌ NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L140
❌ 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.Web/stable/2024-04-01/WebApps.json#L157
❌ 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.Web/stable/2024-04-01/WebApps.json#L157
❌ 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.Web/stable/2024-04-01/WebApps.json#L157
❌ LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L198
❌ LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L207
❌ DeleteResponseCodes Synchronous delete operations must have responses with 200, 204 and default return codes. They also must have no other response codes.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L227
❌ NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L271
❌ LroExtension Operations with a 202 response must specify x-ms-long-running-operation: true. GET operation is excluded from the validation as GET will have 202 only if it is a polling action & hence x-ms-long-running-operation wouldn't be defined
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L288
❌ PatchResponseCodes Synchronous PATCH operations must have responses with 200 and default return codes. They also must not have other response codes.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L288
❌ PatchBodyParametersSchema Properties of a PATCH request body must not have default value, property:netFrameworkVersion.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L311
❌ PatchBodyParametersSchema Properties of a PATCH request body must not be required, property:isPushEnabled.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L311
❌ PatchBodyParametersSchema Properties of a PATCH request body must not have default value, property:http20Enabled.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L311
❌ PatchBodyParametersSchema Properties of a PATCH request body must not be required, property:sourceWebAppId.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L311
❌ LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L329
❌ XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L350
❌ GetCollectionOnlyHasValueAndNextLink Get endpoints for collections of resources must only have the value and nextLink properties in their model.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L384
❌ DeleteResponseCodes Synchronous delete operations must have responses with 200, 204 and default return codes. They also must have no other response codes.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L614
❌ DeleteOperationResponses The delete operation is defined without a 200 or 204 error response implementation,please add it.'
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L646
❌ NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L650
❌ 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.Web/stable/2024-04-01/WebApps.json#L732
❌ LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L774
❌ LroErrorContent Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L783
❌ EvenSegmentedPathForPutOperation API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments).
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L845
❌ PathForNestedResource The path for nested resource doest not meet the valid resource pattern. There is one exception for extension resources with fully qualified path and the author can go ahead and suppress the error(look at https://github.com/Azure/azure-openapi-validator/blob/main/docs/path-for-nested-resource.md#pathfornestedresource for more details)
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L845
❌ XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L846
❌ 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.Web/stable/2024-04-01/WebApps.json#L891
❌ EvenSegmentedPathForPutOperation API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments).
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L945
❌ PathForNestedResource The path for nested resource doest not meet the valid resource pattern. There is one exception for extension resources with fully qualified path and the author can go ahead and suppress the error(look at https://github.com/Azure/azure-openapi-validator/blob/main/docs/path-for-nested-resource.md#pathfornestedresource for more details)
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L945
❌ XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L946
❌ 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.Web/stable/2024-04-01/WebApps.json#L991
❌ EvenSegmentedPathForPutOperation API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments).
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L1095
❌ PathForNestedResource The path for nested resource doest not meet the valid resource pattern. There is one exception for extension resources with fully qualified path and the author can go ahead and suppress the error(look at https://github.com/Azure/azure-openapi-validator/blob/main/docs/path-for-nested-resource.md#pathfornestedresource for more details)
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L1095
❌ 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.Web/stable/2024-04-01/WebApps.json#L1096
❌ PathForResourceAction Path for 'post' method on a resource type MUST follow valid resource naming.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L1151
❌ EvenSegmentedPathForPutOperation API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments).
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L1198
❌ PathForNestedResource The path for nested resource doest not meet the valid resource pattern. There is one exception for extension resources with fully qualified path and the author can go ahead and suppress the error(look at https://github.com/Azure/azure-openapi-validator/blob/main/docs/path-for-nested-resource.md#pathfornestedresource for more details)
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L1198
❌ 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.Web/stable/2024-04-01/WebApps.json#L1199
❌ PathForResourceAction Path for 'post' method on a resource type MUST follow valid resource naming.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L1254
❌ EvenSegmentedPathForPutOperation API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments).
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L1301
❌ PathForNestedResource The path for nested resource doest not meet the valid resource pattern. There is one exception for extension resources with fully qualified path and the author can go ahead and suppress the error(look at https://github.com/Azure/azure-openapi-validator/blob/main/docs/path-for-nested-resource.md#pathfornestedresource for more details)
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L1301
❌ XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L1302
❌ 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.Web/stable/2024-04-01/WebApps.json#L1347
❌ XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L1403
❌ GetCollectionOnlyHasValueAndNextLink Get endpoints for collections of resources must only have the value and nextLink properties in their model.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L1431
❌ EvenSegmentedPathForPutOperation API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments).
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L1449
❌ PathForNestedResource The path for nested resource doest not meet the valid resource pattern. There is one exception for extension resources with fully qualified path and the author can go ahead and suppress the error(look at https://github.com/Azure/azure-openapi-validator/blob/main/docs/path-for-nested-resource.md#pathfornestedresource for more details)
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L1449
❌ 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.Web/stable/2024-04-01/WebApps.json#L1450
❌ PathForResourceAction Path for 'post' method on a resource type MUST follow valid resource naming.
Location: Microsoft.Web/stable/2024-04-01/WebApps.json#L1505
View more details on openapi-pipeline-app