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

[Hub Generated] Publish private branch 'JeetendraJoshi-MSFT-mobilenetwork-Microsoft.MobileNetwork-2023-09-01' #26133

Updated ReadME

883e137
Select commit
Loading
Failed to load commit list.
Merged

[Hub Generated] Publish private branch 'JeetendraJoshi-MSFT-mobilenetwork-Microsoft.MobileNetwork-2023-09-01' #26133

Updated ReadME
883e137
Select commit
Loading
Failed to load commit list.
openapi-pipeline-app / Swagger LintDiff succeeded Oct 9, 2023 in 3m 34s

Swagger LintDiff succeeded

Details

compared tags (via openapi-validator v2.1.6) new version base version
package-2023-09 package-2023-09(883e137) default(main)

The following errors/warnings exist before current PR submission:

Rule Message
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.MobileNetwork/stable/2023-09-01/attachedDataNetwork.json#L38
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/attachedDataNetwork.json#L68
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.MobileNetwork/stable/2023-09-01/dataNetwork.json#L38
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/dataNetwork.json#L65
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.MobileNetwork/stable/2023-09-01/diagnosticsPackage.json#L134
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/diagnosticsPackage.json#L161
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.MobileNetwork/stable/2023-09-01/mobileNetwork.json#L38
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/mobileNetwork.json#L62
OperationsApiSchemaUsesCommonTypes Operations API path must follow the schema provided in the common types.
Location: Microsoft.MobileNetwork/stable/2023-09-01/operation.json#L53
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.MobileNetwork/stable/2023-09-01/packetCapture.json#L143
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/packetCapture.json#L170
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/packetCapture.json#L225
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.MobileNetwork/stable/2023-09-01/packetCoreControlPlane.json#L38
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/packetCoreControlPlane.json#L62
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/packetCoreControlPlane.json#L343
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/packetCoreControlPlane.json#L392
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/packetCoreControlPlane.json#L450
ResourceNameRestriction The resource name parameter 'versionName' should be defined with a 'pattern' restriction.
Location: Microsoft.MobileNetwork/stable/2023-09-01/packetCoreControlPlane.json#L471
ResourceNameRestriction The resource name parameter 'versionName' should be defined with a 'pattern' restriction.
Location: Microsoft.MobileNetwork/stable/2023-09-01/packetCoreControlPlane.json#L547
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.MobileNetwork/stable/2023-09-01/packetCoreDataPlane.json#L38
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/packetCoreDataPlane.json#L65
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.MobileNetwork/stable/2023-09-01/service.json#L38
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/service.json#L65
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.MobileNetwork/stable/2023-09-01/sim.json#L38
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/sim.json#L65
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/sim.json#L276
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.MobileNetwork/stable/2023-09-01/sim.json#L298
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/sim.json#L334
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/sim.json#L395
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.MobileNetwork/stable/2023-09-01/simGroup.json#L38
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/simGroup.json#L62
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.MobileNetwork/stable/2023-09-01/simPolicy.json#L38
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/simPolicy.json#L65
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.MobileNetwork/stable/2023-09-01/site.json#L38
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/site.json#L65
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.MobileNetwork/stable/2023-09-01/site.json#L292
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/site.json#L328
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.MobileNetwork/stable/2023-09-01/slice.json#L38
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.MobileNetwork/stable/2023-09-01/slice.json#L65
⚠️ LatestVersionOfCommonTypesMustBeUsed Use the latest version v5 of managedidentity.json.
Location: Microsoft.MobileNetwork/stable/2023-09-01/common.json#L540
⚠️ EnumInsteadOfBoolean Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum.
Location: Microsoft.MobileNetwork/stable/2023-09-01/operation.json#L77
⚠️ AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
Location: Microsoft.MobileNetwork/stable/2023-09-01/operation.json#L86
⚠️ PostOperationIdContainsUrlVerb OperationId should contain the verb: 'uploadsims' in:'Sims_BulkUpload'. Consider updating the operationId
Location: Microsoft.MobileNetwork/stable/2023-09-01/sim.json#L244
⚠️ PostOperationIdContainsUrlVerb OperationId should contain the verb: 'deletesims' in:'Sims_BulkDelete'. Consider updating the operationId
Location: Microsoft.MobileNetwork/stable/2023-09-01/sim.json#L302
⚠️ PostOperationIdContainsUrlVerb OperationId should contain the verb: 'uploadencryptedsims' in:'Sims_BulkUploadEncrypted'. Consider updating the operationId
Location: Microsoft.MobileNetwork/stable/2023-09-01/sim.json#L363
⚠️ AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
Location: Microsoft.MobileNetwork/stable/2023-09-01/sim.json#L604