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] Review request for Microsoft.RecoveryServices to add version stable/2023-01-15 #22431

Conversation

profDisarray
Copy link
Contributor

@profDisarray profDisarray commented Feb 2, 2023

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.

ARM API Information (Control Plane)

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:

  1. 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
  2. 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.
  3. When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
  4. 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):

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

Applicability: ⚠️

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.

@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Feb 2, 2023

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]
There are no breaking changes.
️❌Breaking Change(Cross-Version): 349 Errors, 366 Warnings failed [Detail]
compared swaggers (via Oad v0.10.4)] new version base version
bms.json 2023-01-15(47ae9c4) 2023-01-01(main)
bms.json 2023-01-15(47ae9c4) 2022-09-30-preview(main)

The following breaking changes are detected by comparison with the latest stable version:

Only 23 items are listed, please refer to log for more details.

Rule Message
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupstorageconfig/vaultstorageconfig' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L21:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/Subscriptions/{subscriptionId}/providers/Microsoft.RecoveryServices/locations/{azureRegion}/backupPreValidateProtection' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L164:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/Subscriptions/{subscriptionId}/providers/Microsoft.RecoveryServices/locations/{azureRegion}/backupStatus' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L209:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/Subscriptions/{subscriptionId}/providers/Microsoft.RecoveryServices/locations/{azureRegion}/backupValidateFeatures' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L254:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/backupProtectionIntent/{intentObjectName}' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L299:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupProtectionIntents' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L460:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupUsageSummaries' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L517:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/providers/Microsoft.RecoveryServices/operations' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L577:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupconfig/vaultconfig' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L608:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupEncryptionConfigs/backupResourceEncryptionConfig' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L757:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/privateEndpointConnections/{privateEndpointConnectionName}' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L851:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/privateEndpointConnections/{privateEndpointConnectionName}/operationsStatus/{operationId}' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L1023:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupstorageconfig/vaultstorageconfig/operationStatus/{operationId}' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L1082:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupstorageconfig/vaultstorageconfig/prepareDataMove' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L1133:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupstorageconfig/vaultstorageconfig/operationResults/{operationId}' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L1188:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupstorageconfig/vaultstorageconfig/triggerDataMove' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L1242:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L1297:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}/operationResults/{operationId}' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L1520:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}/recoveryPoints' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L1599:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}/recoveryPoints/{recoveryPointId}' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L1676:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}/recoveryPoints/{recoveryPointId}/restore' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L1749:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupPolicies' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L1844:5
1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupPolicies/{policyName}' removed or restructured?
Old: Microsoft.RecoveryServices/stable/2023-01-01/bms.json#L1906:5


The following breaking changes are detected by comparison with the latest preview version:

Only 23 items are listed, please refer to log for more details.

Rule Message
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupstorageconfig/vaultstorageconfig' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L21:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/Subscriptions/{subscriptionId}/providers/Microsoft.RecoveryServices/locations/{azureRegion}/backupPreValidateProtection' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L164:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/Subscriptions/{subscriptionId}/providers/Microsoft.RecoveryServices/locations/{azureRegion}/backupStatus' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L209:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/Subscriptions/{subscriptionId}/providers/Microsoft.RecoveryServices/locations/{azureRegion}/backupValidateFeatures' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L254:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/backupProtectionIntent/{intentObjectName}' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L299:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupProtectionIntents' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L460:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupUsageSummaries' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L517:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/providers/Microsoft.RecoveryServices/operations' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L577:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupconfig/vaultconfig' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L608:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupEncryptionConfigs/backupResourceEncryptionConfig' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L757:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/privateEndpointConnections/{privateEndpointConnectionName}' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L851:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/privateEndpointConnections/{privateEndpointConnectionName}/operationsStatus/{operationId}' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L1023:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupstorageconfig/vaultstorageconfig/operationStatus/{operationId}' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L1082:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupstorageconfig/vaultstorageconfig/prepareDataMove' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L1133:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupstorageconfig/vaultstorageconfig/operationResults/{operationId}' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L1188:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupstorageconfig/vaultstorageconfig/triggerDataMove' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L1242:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L1297:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}/operationResults/{operationId}' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L1520:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}/recoveryPoints' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L1599:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}/recoveryPoints/{recoveryPointId}' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L1676:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName}/recoveryPoints/{recoveryPointId}/restore' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L1749:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupPolicies' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L1844:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupPolicies/{policyName}' removed or restructured?
Old: Microsoft.RecoveryServices/preview/2022-09-30-preview/bms.json#L1906:5
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️❌LintDiff: 56 Errors, 24 Warnings failed [Detail]
compared tags (via openapi-validator v2.0.0) new version base version
package-passivestamp-2023-01-15 package-passivestamp-2023-01-15(47ae9c4) default(main)

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

Only 23 items are listed, please refer to log for more details.

Rule Message Related RPC [For API reviewers]
OperationsAPIImplementation Operations API must be implemented for 'Microsoft.RecoveryServices'.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L1
ResourceNameRestriction The resource name parameter 'vaultName' should be defined with a 'pattern' restriction.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L21
RPC-Uri-V1-05
ParametersOrder The parameters:vaultName,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L22
TrackedResourcePatchOperation Tracked resource 'AADPropertiesResource' must have patch operation that at least supports the update of tags.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L87
RPC-Patch-V1-03
TrackedResourcesMustHavePut The tracked resource AADPropertiesResource does not have a corresponding put operation.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L87
RPC-Put-V1-22
PostOperationAsyncResponseValidation An async POST operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'location' on 'x-ms-long-running-operation-options'
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L138
RPC-Async-V1-11
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L171
RPC-Async-V1-07
GetOperation200 The get operation should only return 200.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L345
RPC-Get-V1-01
LroLocationHeader A 202 response should include an Location response header.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L345
RPC-Async-V1-07
ResourceNameRestriction The resource name parameter 'vaultName' should be defined with a 'pattern' restriction.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L409
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'fabricName' should be defined with a 'pattern' restriction.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L409
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'containerName' should be defined with a 'pattern' restriction.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L409
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'protectedItemName' should be defined with a 'pattern' restriction.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L409
RPC-Uri-V1-05
ParametersOrder The parameters:vaultName,resourceGroupName,fabricName,containerName,protectedItemName,recoveryPointId should be kept in the same order as they present in the path.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L410
AllResourcesMustHaveDelete The resource BackupResourceConfigResource does not have a corresponding delete operation.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L495
PathForNestedResource The path for nested resource doest not meet the valid resource pattern.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L495
RPC-Uri-V1-06,RPC-Put-V1-02
PutGetPatchResponseSchema /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupstorageconfig/vaultstorageconfig has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L495
RPC-Put-V1-12
ResourceNameRestriction The resource name parameter 'vaultName' should be defined with a 'pattern' restriction.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L495
RPC-Uri-V1-05
ParametersOrder The parameters:vaultName,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L496
ParametersOrder The parameters:vaultName,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L539
ParametersOrder The parameters:vaultName,resourceGroupName should be kept in the same order as they present in the path.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L591
UnSupportedPatchProperties The patch operation body parameter schema should not contains property name.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L610
RPC-Patch-V1-02
UnSupportedPatchProperties The patch operation body parameter schema should not contains property type.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L610
RPC-Patch-V1-02


The following errors/warnings exist before current PR submission:

Only 23 items are listed, please refer to log for more details.

Rule Message
XmsParameterLocation The parameter 'SubscriptionId' 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.RecoveryServices/stable/2023-01-15/bms.json#L4489
XmsParameterLocation The parameter 'ApiVersion' 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.RecoveryServices/stable/2023-01-15/bms.json#L4504
⚠️ DeprecatedXmsCodeGenerationSetting The x-ms-code-generation-setting extension is being deprecated. Please remove it and move settings to readme file for code generation.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L6
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L1507
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L2223
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L2227
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L2290
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L2294
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L2298
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L2351
⚠️ AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L2395
⚠️ SchemaDescriptionOrTitle Schema should have a description or title.
Location: Microsoft.RecoveryServices/stable/2023-01-15/bms.json#L2585
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L2596
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L2796
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L2800
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L2838
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L2860
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L3031
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L3040
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L3051
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L3059
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L3156
⚠️ 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.RecoveryServices/stable/2023-01-15/bms.json#L3160
️❌Avocado: 1 Errors, 0 Warnings failed [Detail]
Rule Message
MULTIPLE_DEFAULT_TAGS The readme file has more than one default tag.
readme: specification/recoveryservicesbackup/resource-manager/readme.md
️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
️⚠️~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]

API Test is not triggered due to precheck failure. Check pipeline log for details.

️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️CadlAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️️✔️TypeSpec Validation succeeded [Detail] [Expand]
Validation passes for TypeSpec Validation.
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Posted by Swagger Pipeline | How to fix these errors?

@openapi-workflow-bot
Copy link

Hi, @profDisarray Thanks for your PR. I am workflow bot for review process. Here are some small tips.

  • Please ensure to do self-check against checklists in first PR comment.
  • PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.
  • For specs comparison cross API versions, Use API Specs Comparison Report Generator
  • If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?

  • Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected]

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Feb 2, 2023

    Swagger Generation Artifacts

    ️🔄ApiDocPreview inProgress [Detail]
    ️⌛SDK Breaking Change Tracking pending [Detail]
    ️⌛ azure-sdk-for-net-track2 pending [Detail]
    ️⌛ azure-sdk-for-python-track2 pending [Detail]
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Feb 2, 2023

    Generated ApiView

    Language Package Name ApiView Link
    Go sdk/resourcemanager/recoveryservices/armrecoveryservicesbackup https://apiview.dev/Assemblies/Review/851cd55c263246a1af98ac0171f32884
    Java azure-resourcemanager-recoveryservicesbackup There is no API change compared with the previous version
    .Net Azure.ResourceManager.RecoveryServicesBackup https://apiview.dev/Assemblies/Review/0e2cc7b50da543f6b65eb358e3f95a7d
    JavaScript @azure/arm-recoveryservicesbackup There is no API change compared with the previous version

    @AzureRestAPISpecReview AzureRestAPISpecReview added BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required new-api-version resource-manager labels Feb 2, 2023
    @openapi-workflow-bot
    Copy link

    Hi @profDisarray, 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.

    @profDisarray profDisarray marked this pull request as ready for review February 7, 2023 11:20
    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Feb 7, 2023

    Swagger Generation Artifacts

    ️️✔️ApiDocPreview succeeded [Detail] [Expand]
     Please click here to preview with your @microsoft account. 
    ️️✔️SDK Breaking Change Tracking succeeded [Detail] [Expand]

    Breaking Changes Tracking



    ️️✔️ azure-sdk-for-net-track2 succeeded [Detail] [Expand]
    ️⚠️ azure-sdk-for-python-track2 warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from 7dc9785. SDK Automation 14.0.0
      command	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] npm notice
      cmderr	[automation_generate.sh] npm notice New minor version of npm available! 9.5.0 -> 9.6.2
      cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.2>
      cmderr	[automation_generate.sh] npm notice Run `npm install -g [email protected]` to update!
      cmderr	[automation_generate.sh] npm notice
    • ️✔️track2_azure-mgmt-recoveryservicesbackup [View full logs]  [Release SDK Changes]
      info	[Changelog]
    ️️✔️ azure-sdk-for-java succeeded [Detail] [Expand]
    ️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from 7dc9785. SDK Automation 14.0.0
      command	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/recoveryservices/armrecoveryservicesbackup [View full logs]  [Release SDK Changes]
      info	[Changelog] ### Other Changes
      info	[Changelog]
      info	[Changelog] Total 0 breaking change(s), 0 additive change(s).
    ️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from 7dc9785. SDK Automation 14.0.0
      command	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
      cmderr	[automation_generate.sh] [ERROR] Cannot generate changelog because the codes of local and npm may be the same.
    • ️✔️@azure/arm-recoveryservicesbackup [View full logs]  [Release SDK Changes]
      info	[Changelog]
      error	breakingChangeTracking is enabled, but version or changelogItem is not found in output.
    ️⚠️ azure-resource-manager-schemas warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from 7dc9785. Schema Automation 14.0.0
      command	.sdkauto/initScript.sh ../azure-resource-manager-schemas_tmp/initInput.json ../azure-resource-manager-schemas_tmp/initOutput.json
      cmderr	[initScript.sh]
      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
    • ️✔️recoveryservicesbackup [View full logs]  [Release Schema Changes]
    ️❌ azure-powershell failed [Detail]
    • Failed [Logs]Release - Generate from 7dc9785. SDK Automation 14.0.0
      command	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.recoveryservicesbackup.DefaultTag [View full logs]  [Release SDK Changes]
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-workflow-bot
    Copy link

    Hi @profDisarray, 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.

    TaskHow to fixPriority
    AvocadoFix-AvocadoHigh
    Semantic validationFix-SemanticValidation-ErrorHigh
    Model validationFix-ModelValidation-ErrorHigh
    LintDiffFix-LintDiffhigh
    If you need further help, please feedback via swagger feedback.

    @profDisarray
    Copy link
    Contributor Author

    /azp run unifiedPipeline

    @azure-pipelines
    Copy link

    No pipelines are associated with this pull request.

    @profDisarray
    Copy link
    Contributor Author

    /azp run

    @azure-pipelines
    Copy link

    Azure Pipelines successfully started running 1 pipeline(s).

    @raych1 raych1 added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Feb 21, 2023
    @NetRock NetRock added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Feb 21, 2023
    @openapi-workflow-bot openapi-workflow-bot bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Feb 21, 2023
    @raych1
    Copy link
    Member

    raych1 commented Mar 10, 2023

    Hi @profDisarray, 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.

    @profDisarray , can you follow above instructions to get breaking change reviewed?

    @profDisarray
    Copy link
    Contributor Author

    profDisarray commented Mar 10, 2023

    @profDisarray , can you follow above instructions to get breaking change reviewed?

    Hi @raych1, we are having the discussion with the respective team over a mail thread. There are some confusions. I will provide an update when everything is resolved and the breaking change is approved.

    @raych1 raych1 added the Reviewed-ChangesRequested <valid label in PR review process>add this label when assignee request changes after review label Mar 13, 2023
    @raych1
    Copy link
    Member

    raych1 commented Mar 13, 2023

    @profDisarray , can you follow above instructions to get breaking change reviewed?

    Hi @raych1, we are having the discussion with the respective team over a mail thread. There are some confusions. I will provide an update when everything is resolved and the breaking change is approved.

    sounds good.

    @JeffreyRichter JeffreyRichter added the Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 label Mar 20, 2023
    @raych1
    Copy link
    Member

    raych1 commented Mar 24, 2023

    @profDisarray , can you resolve the conflicts and fix the CI check failures?

    @profDisarray
    Copy link
    Contributor Author

    @raych1 Resolved the conflicts. Avocado and lintDiff checks are expected to fail.
    Avocado checks are overridden for recoveryServices PRs. Latest merged PR #22260.

    @profDisarray
    Copy link
    Contributor Author

    For LintDiff failures:
    The new api version is based on an older API version and not the latest. It only has a subset of APIs. We use this API version based routing to route the requests to the passive region in case of a disaster.

    You can refer to this PR where similar thing was done #17044

    @raych1 raych1 merged commit 7dc9785 into main Mar 28, 2023
    @raych1 raych1 deleted the profDisarray-recoveryservicesbackup-Microsoft.RecoveryServices-2023-01-15 branch March 28, 2023 07:52
    JoshLove-msft pushed a commit to JoshLove-msft/azure-rest-api-specs that referenced this pull request Apr 25, 2023
    …version stable/2023-01-15 (Azure#22431)
    
    * Adds base for updating Microsoft.RecoveryServices from version stable/2021-11-15 to version 2023-01-15
    
    * Updates readme
    
    * Updates API version in new specs and examples
    
    * Adds RecoveryPointProperties for 2023-01-15
    
    * Adds RecoveryPointProperties at missed places
    
    * Fixes API version in examples
    
    * Fixes model validation errors
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    Approved-Avocado Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 Approved-LintDiff ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required CI-FixRequiredOnFailure new-api-version Recovery Services Backup resource-manager Reviewed-ChangesRequested <valid label in PR review process>add this label when assignee request changes after review
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    5 participants