Update listVault.json
ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow. Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:
- What's the purpose of the update?
- [ ] new service onboarding
- [ ] new API version
- [ ] update existing version for new feature
- [ ] update existing version to fix swagger quality issue in s360
- [ ] Other, please clarify
- When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
- When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
- By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.
Contribution checklist (MS Employees Only):
- [ ] I commit to follow the Breaking Change Policy of "no breaking changes"
- [ ] I have reviewed the documentation for the workflow.
- [ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.
- Change to data plane APIs
- Adding new properties
- All removals
Otherwise your PR may be subject to ARM review requirements. Complete the following:
-
[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
- Adding a new service
- Adding new API(s)
- Adding a new API version -[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.
-
[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
-
[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.
Hi, @rahulalapati43 Thanks for your PR. I am workflow bot for review process. Here are some small tips.
Swagger Validation Report
️️✔️BreakingChange succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
| compared swaggers (via Oad v0.10.2)] | new version | base version |
|---|---|---|
| keyvault.json | 2022-02-01-preview(e60abf3) | 2021-10-01(main) |
| keyvault.json | 2022-02-01-preview(e60abf3) | 2021-11-01-preview(main) |
️⚠️LintDiff: 0 Warnings warning [Detail]
| compared tags (via openapi-validator v2.0.0) | new version | base version |
|---|---|---|
| package-preview-2022-02 | package-preview-2022-02(e60abf3) | package-preview-2022-02(dev-keyvault-Microsoft.KeyVault-2022-02-01-preview-swagger-completeness) |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
GetCollectionResponseSchema |
The response in the GET collection operation 'Keys_List' does not match the response definition in the individual GET operation 'Keys_Get' . Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L12 |
GetCollectionResponseSchema |
The response in the GET collection operation 'Keys_ListVersions' does not match the response definition in the individual GET operation 'Keys_GetVersion' . Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L12 |
CreateOperationAsyncResponseValidation |
An async PUT operation must set long running operation options 'x-ms-long-running-operation-options' Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L14 |
AllResourcesMustHaveDelete |
The resource VaultAccessPolicyParameters does not have a corresponding delete operation. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L267 |
TrackedResourcePatchOperation |
Tracked resource 'VaultAccessPolicyParameters' must have patch operation that at least supports the update of tags. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L267 |
ResourceNameRestriction |
The resource name parameter 'vaultName' should be defined with a 'pattern' restriction. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L511 |
ParametersOrder |
The parameters:vaultName,location should be kept in the same order as they present in the path. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L512 |
ResourceNameRestriction |
The resource name parameter 'vaultName' should be defined with a 'pattern' restriction. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L567 |
ParametersOrder |
The parameters:vaultName,location should be kept in the same order as they present in the path. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L568 |
PostOperationAsyncResponseValidation |
An async POST operation must set long running operation options 'x-ms-long-running-operation-options' Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L568 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L601 |
PathContainsResourceType |
The path for the CURD methods do not contain a resource type. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L624 |
ResourceNameRestriction |
The resource name parameter 'privateEndpointConnectionName' should be defined with a 'pattern' restriction. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L750 |
TrackedResourcePatchOperation |
Tracked resource 'PrivateEndpointConnection' must have patch operation that at least supports the update of tags. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L750 |
GetOperation200 |
The get operation should only return 200. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L789 |
DeleteOperationAsyncResponseValidation |
An async DELETE operation must set long running operation options 'x-ms-long-running-operation-options' Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L869 |
DeleteResponseBodyEmpty |
The delete response body must be empty. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L903 |
GuidUsage |
Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L1067 |
GuidUsage |
Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L1076 |
GuidUsage |
Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L1216 |
ProvisioningStateValidation |
ProvisioningState must have terminal states: Succeeded, Failed and Canceled. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L1296 |
GuidUsage |
Usage of Guid is not recommended. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L1333 |
NestedResourcesMustHaveListOperation |
The nested resource 'VaultAccessPolicyParameters' does not have list operation, please add it. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L1511 |
XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L1780 |
XmsParameterLocation |
The parameter 'SubscriptionIdParameter' is defined in global parameters section without 'x-ms-parameter-location' extension. This would add the parameter as the client property. Please ensure that this is exactly you want. If so, apply the extension 'x-ms-parameter-location': 'client'. Else, apply the extension 'x-ms-parameter-location': 'method'. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L2030 |
XmsParameterLocation |
The parameter 'ApiVersionParameter' is defined in global parameters section without 'x-ms-parameter-location' extension. This would add the parameter as the client property. Please ensure that this is exactly you want. If so, apply the extension 'x-ms-parameter-location': 'client'. Else, apply the extension 'x-ms-parameter-location': 'method'. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L2062 |
| :warning: PutRequestResponseScheme | A PUT operation request body schema should be the same as its 200 response schema, to allow reusing the same entity between GET and PUT. If the schema of the PUT request body is a superset of the GET response body, make sure you have a PATCH operation to make the resource updatable. Operation: 'Vaults_CreateOrUpdate' Request Model: 'parameters[3].schema' Response Model: 'responses[200].schema' Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L14 |
| :warning: XmsLongRunningOperationOptions | The x-ms-long-running-operation-options should be specified explicitly to indicate the type of response header to track the async operation. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L14 |
| :warning: RequiredReadOnlySystemData | The response of operation:'Vaults_UpdateAccessPolicy' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L268 |
| :warning: PutInOperationName | 'PUT' operation 'Vaults_UpdateAccessPolicy' should use method name 'Create'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.KeyVault/preview/2022-02-01-preview/keyvault.json#L272 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Swagger Generation Artifacts
️️✔️ApiDocPreview succeeded [Detail] [Expand]
Please click here to preview with your @microsoft account.
️⚠️SDK Breaking Change Tracking warning [Detail]
Breaking Changes Tracking
⚠️azure-sdk-for-go - sdk/resourcemanager/keyvault/armkeyvault - 1.1.0-beta.2+ Struct `CloudErrorBody` has been removed + Struct `CloudError` has been removed
⚠️azure-sdk-for-js - @azure/arm-keyvault - 3.0.0-beta.1+ Interface ManagedHsmsListByResourceGroupNextOptionalParams no longer has parameter top + Interface ManagedHsmsListBySubscriptionNextOptionalParams no longer has parameter top + Interface MhsmPrivateEndpointConnectionsDeleteHeaders no longer has parameter retryAfter + Interface SecretsListNextOptionalParams no longer has parameter top + Interface VaultsListByResourceGroupNextOptionalParams no longer has parameter top + Interface VaultsListBySubscriptionNextOptionalParams no longer has parameter top + Interface VaultsListNextOptionalParams no longer has parameter top
️⚠️ azure-sdk-for-net-track2 warning [Detail]
⚠️Warning [Logs] Generate from 16b2619a7a75c7903aab1c26510d75e57627b031. SDK Automation 14.0.0command pwsh ./eng/scripts/Automation-Sdk-Init.ps1 ../azure-sdk-for-net_tmp/initInput.json ../azure-sdk-for-net_tmp/initOutput.json command pwsh ./eng/scripts/Invoke-GenerateAndBuildV2.ps1 ../azure-sdk-for-net_tmp/generateInput.json ../azure-sdk-for-net_tmp/generateOutput.json warn No file changes detected after generation
️✔️Azure.ResourceManager.KeyVault [View full logs]info [Changelog]
️⚠️ azure-sdk-for-python-track2 warning [Detail]
⚠️Warning [Logs] Generate from 16b2619a7a75c7903aab1c26510d75e57627b031. SDK Automation 14.0.0command sh scripts/automation_init.sh ../azure-sdk-for-python_tmp/initInput.json ../azure-sdk-for-python_tmp/initOutput.json cmderr [automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed. command sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json cmderr [automation_generate.sh] cmderr [automation_generate.sh] npm notice New major version of npm available! 8.19.2 -> 9.3.0 cmderr [automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.3.0> cmderr [automation_generate.sh] npm notice Run `npm install -g [email protected]` to update! cmderr [automation_generate.sh] npm notice
️✔️track2_azure-mgmt-keyvault [View full logs] [Preview SDK Changes]info [Changelog] ### Features Added info [Changelog] info [Changelog] - Model ManagedHsmProperties has a new parameter security_domain_properties
️⚠️ azure-sdk-for-java warning [Detail]
⚠️Warning [Logs] Generate from 16b2619a7a75c7903aab1c26510d75e57627b031. SDK Automation 14.0.0command ./eng/mgmt/automation/init.sh ../azure-sdk-for-java_tmp/initInput.json ../azure-sdk-for-java_tmp/initOutput.json cmderr [init.sh] [notice] A new release of pip available: 22.3 -> 22.3.1 cmderr [init.sh] [notice] To update, run: pip install --upgrade pip cmderr [init.sh] [notice] A new release of pip available: 22.3 -> 22.3.1 cmderr [init.sh] [notice] To update, run: pip install --upgrade pip command ./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json
️✔️azure-resourcemanager-keyvault-generated [View full logs] [Preview SDK Changes]
️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
️✔️Succeeded [Logs] Generate from 16b2619a7a75c7903aab1c26510d75e57627b031. SDK Automation 14.0.0command sh ./eng/scripts/automation_init.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json command generator automation-v2 ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
️✔️sdk/resourcemanager/keyvault/armkeyvault [View full logs] [Preview SDK Changes] Breaking Change Detectedinfo [Changelog] ### Breaking Changes info [Changelog] info [Changelog] - Struct `CloudError` has been removed info [Changelog] - Struct `CloudErrorBody` has been removed info [Changelog] info [Changelog] ### Features Added info [Changelog] info [Changelog] - New type alias `ActivationStatus` with values `ActivationStatusActive`, `ActivationStatusFailed`, `ActivationStatusNotActivated`, `ActivationStatusUnknown` info [Changelog] - New function `*ManagedHsmsClient.CheckMhsmNameAvailability(context.Context, CheckMhsmNameAvailabilityParameters, *ManagedHsmsClientCheckMhsmNameAvailabilityOptions) (ManagedHsmsClientCheckMhsmNameAvailabilityResponse, error)` info [Changelog] - New struct `CheckMhsmNameAvailabilityParameters` info [Changelog] - New struct `CheckMhsmNameAvailabilityResult` info [Changelog] - New struct `ManagedHSMSecurityDomainProperties` info [Changelog] - New field `Etag` in struct `MHSMPrivateEndpointConnectionItem` info [Changelog] - New field `ID` in struct `MHSMPrivateEndpointConnectionItem` info [Changelog] - New field `SecurityDomainProperties` in struct `ManagedHsmProperties` info [Changelog] info [Changelog] Total 4 breaking change(s), 14 additive change(s).
️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]
️✔️Succeeded [Logs] Generate from 16b2619a7a75c7903aab1c26510d75e57627b031. SDK Automation 14.0.0command sh .scripts/automation_init.sh ../azure-sdk-for-js_tmp/initInput.json ../azure-sdk-for-js_tmp/initOutput.json warn File azure-sdk-for-js_tmp/initOutput.json not found to read command sh .scripts/automation_generate.sh ../azure-sdk-for-js_tmp/generateInput.json ../azure-sdk-for-js_tmp/generateOutput.json
️✔️@azure/arm-keyvault [View full logs] [Preview SDK Changes] Breaking Change Detectedinfo [Changelog] **Features** info [Changelog] info [Changelog] - Added operation ManagedHsms.checkMhsmNameAvailability info [Changelog] - Added Interface Action info [Changelog] - Added Interface CheckMhsmNameAvailabilityParameters info [Changelog] - Added Interface CheckMhsmNameAvailabilityResult info [Changelog] - Added Interface Key info [Changelog] - Added Interface KeyReleasePolicy info [Changelog] - Added Interface KeyRotationPolicyAttributes info [Changelog] - Added Interface LifetimeAction info [Changelog] - Added Interface ManagedHsm info [Changelog] - Added Interface ManagedHsmsCheckMhsmNameAvailabilityOptionalParams info [Changelog] - Added Interface ManagedHsmsCreateOrUpdateHeaders info [Changelog] - Added Interface ManagedHsmsDeleteHeaders info [Changelog] - Added Interface ManagedHSMSecurityDomainProperties info [Changelog] - Added Interface ManagedHsmsPurgeDeletedHeaders info [Changelog] - Added Interface ManagedHsmsUpdateHeaders info [Changelog] - Added Interface MhsmPrivateEndpointConnection info [Changelog] - Added Interface MhsmPrivateLinkResource info [Changelog] - Added Interface PrivateEndpointConnection info [Changelog] - Added Interface PrivateLinkResource info [Changelog] - Added Interface RotationPolicy info [Changelog] - Added Interface Secret info [Changelog] - Added Interface SecretAttributes info [Changelog] - Added Interface Trigger info [Changelog] - Added Type Alias ActivationStatus info [Changelog] - Added Type Alias KeyRotationPolicyActionType info [Changelog] - Added Type Alias ManagedHsmsCheckMhsmNameAvailabilityResponse info [Changelog] - Added Type Alias ManagedHsmsPurgeDeletedResponse info [Changelog] - Interface KeyProperties has a new optional parameter releasePolicy info [Changelog] - Interface KeyProperties has a new optional parameter rotationPolicy info [Changelog] - Interface ManagedHsmProperties has a new optional parameter securityDomainProperties info [Changelog] - Interface MhsmPrivateEndpointConnectionItem has a new optional parameter etag info [Changelog] - Interface MhsmPrivateEndpointConnectionItem has a new optional parameter id info [Changelog] - Added Enum KnownActivationStatus info [Changelog] - Enum KnownJsonWebKeyOperation has a new value Release info [Changelog] - Enum KnownKeyPermissions has a new value Getrotationpolicy info [Changelog] - Enum KnownKeyPermissions has a new value Release info [Changelog] - Enum KnownKeyPermissions has a new value Rotate info [Changelog] - Enum KnownKeyPermissions has a new value Setrotationpolicy info [Changelog] - Added function getContinuationToken info [Changelog] info [Changelog] **Breaking Changes** info [Changelog] info [Changelog] - Interface ManagedHsmsListByResourceGroupNextOptionalParams no longer has parameter top info [Changelog] - Interface ManagedHsmsListBySubscriptionNextOptionalParams no longer has parameter top info [Changelog] - Interface MhsmPrivateEndpointConnectionsDeleteHeaders no longer has parameter retryAfter info [Changelog] - Interface SecretsListNextOptionalParams no longer has parameter top info [Changelog] - Interface VaultsListByResourceGroupNextOptionalParams no longer has parameter top info [Changelog] - Interface VaultsListBySubscriptionNextOptionalParams no longer has parameter top info [Changelog] - Interface VaultsListNextOptionalParams no longer has parameter top
️⚠️ azure-resource-manager-schemas warning [Detail]
⚠️Warning [Logs] Generate from 16b2619a7a75c7903aab1c26510d75e57627b031. Schema Automation 14.0.0command .sdkauto/initScript.sh ../azure-resource-manager-schemas_tmp/initInput.json ../azure-resource-manager-schemas_tmp/initOutput.json cmderr [initScript.sh] WARN old lockfile cmderr [initScript.sh] npm WARN old lockfile The package-lock.json file was created with an old version of npm, cmderr [initScript.sh] npm WARN old lockfile so supplemental metadata must be fetched from the registry. cmderr [initScript.sh] npm WARN old lockfile cmderr [initScript.sh] npm WARN old lockfile This is a one-time fix-up, please be patient... cmderr [initScript.sh] npm WARN old lockfile warn File azure-resource-manager-schemas_tmp/initOutput.json not found to read command .sdkauto/generateScript.sh ../azure-resource-manager-schemas_tmp/generateInput.json ../azure-resource-manager-schemas_tmp/generateOutput.json
️✔️keyvault [View full logs] [Preview Schema Changes]
️❌ azure-powershell failed [Detail]
❌Failed [Logs] Generate from 16b2619a7a75c7903aab1c26510d75e57627b031. SDK Automation 14.0.0command sh ./tools/SwaggerCI/init.sh ../azure-powershell_tmp/initInput.json ../azure-powershell_tmp/initOutput.json command pwsh ./tools/SwaggerCI/psci.ps1 ../azure-powershell_tmp/generateInput.json ../azure-powershell_tmp/generateOutput.json
❌Az.keyvault [View full logs] [Preview SDK Changes]
Generated ApiView
| Language | Package Name | ApiView Link |
|---|---|---|
| Go | sdk/resourcemanager/keyvault/armkeyvault | https://apiview.dev/Assemblies/Review/0e5e119f4d8e4c6ca42b8e1a9a49cd04 |
| Java | azure-resourcemanager-keyvault-generated | https://apiview.dev/Assemblies/Review/01b553ed05484d2a895fee18c9355047 |
| .Net | Azure.ResourceManager.KeyVault | There is no API change compared with the previous version |
| JavaScript | @azure/arm-keyvault | https://apiview.dev/Assemblies/Review/255c06e0f80e4fe384395c4d3d7c2e3f |
Hi @rahulalapati43, Your PR has some issues. Please fix the CI sequentially by following the order of Avocado, semantic validation, model validation, breaking change, lintDiff. If you have any questions, please post your questions in this channel https://aka.ms/swaggersupport.
| Task | How to fix | Priority |
|---|---|---|
| Avocado | Fix-Avocado | High |
| Semantic validation | Fix-SemanticValidation-Error | High |
| Model validation | Fix-ModelValidation-Error | High |
| LintDiff | Fix-LintDiff | high |
Hi @rahulalapati43, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki. If you want to know the production traffic statistic, please see ARM Traffic statistic. If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback. Note: To avoid breaking change, you can refer to Shift Left Solution for detecting breaking change in early phase at your service code repository.
Hi @rahulalapati43, one or multiple validation error/warning suppression(s) is detected in your PR. Please follow the Swagger-Suppression-Process to get approval.
/azp run
Azure Pipelines successfully started running 1 pipeline(s).
/azp run
Azure Pipelines successfully started running 1 pipeline(s).