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

Additional TieringPolicy and ProtectedItemExtendedInfo details for Microsoft.RecoveryServices version 2021-12-01 #17517

Merged
merged 10 commits into from
Mar 11, 2022
Merged

Conversation

anjorsh
Copy link
Member

@anjorsh anjorsh commented Jan 26, 2022

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

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. If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.
    • SDK of .NET (need service team to ensure code readiness)
    • SDK of Python
    • SDK of Java
    • SDK of Js
    • SDK of Go
    • PowerShell
    • CLI
    • Terraform
    • No refresh required for updates in this PR

Contribution checklist:

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 label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

    • Adding a new service
    • Adding new API(s)
    • Adding a new API version
      -[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. 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 any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

  • Removing API(s) in a stable version
  • Removing properties in a stable version
  • Removing API version(s) in a stable version
  • Updating API in a stable or public preview version with Breaking Change Validation errors
  • Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

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.

Please follow the link to find more details on PR review process.

@openapi-workflow-bot
Copy link

Hi, @anjorsh 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. vsswagger@microsoft.com

    @openapi-workflow-bot
    Copy link

    [Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks.

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Jan 26, 2022

    Swagger Validation Report

    ️❌BreakingChange: 7 Errors, 0 Warnings failed [Detail]
    Rule Message
    1045 - AddedOptionalProperty The new version has a new optional property 'oldestRecoveryPointInVault' that was not found in the old version.
    New: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L5451:7
    Old: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L5451:7
    1045 - AddedOptionalProperty The new version has a new optional property 'oldestRecoveryPointInArchive' that was not found in the old version.
    New: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L5451:7
    Old: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L5451:7
    1045 - AddedOptionalProperty The new version has a new optional property 'newestRecoveryPointInArchive' that was not found in the old version.
    New: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L5451:7
    Old: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L5451:7
    1045 - AddedOptionalProperty The new version has a new optional property 'tieringPolicy' that was not found in the old version.
    New: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L5491:7
    Old: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L5476:7
    1045 - AddedOptionalProperty The new version has a new optional property 'oldestRecoveryPointInVault' that was not found in the old version.
    New: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L5826:7
    Old: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L5804:7
    1045 - AddedOptionalProperty The new version has a new optional property 'oldestRecoveryPointInArchive' that was not found in the old version.
    New: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L5826:7
    Old: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L5804:7
    1045 - AddedOptionalProperty The new version has a new optional property 'newestRecoveryPointInArchive' that was not found in the old version.
    New: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L5826:7
    Old: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L5804:7
    ️⚠️LintDiff: 0 Warnings warning [Detail]
    The following errors/warnings exist before current PR submission:

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

    Rule Message
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupstorageconfig/vaultstorageconfig'
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L21
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/Subscriptions/{subscriptionId}/providers/Microsoft.RecoveryServices/locations/{azureRegion}/backupPreValidateProtection'
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L164
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/Subscriptions/{subscriptionId}/providers/Microsoft.RecoveryServices/locations/{azureRegion}/backupStatus'
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L209
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/Subscriptions/{subscriptionId}/providers/Microsoft.RecoveryServices/locations/{azureRegion}/backupValidateFeatures'
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L254
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/backupProtectionIntent/{intentObjectName}'
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L299
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupProtectionIntents'
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L460
    R3021 - PathResourceTypeNameCamelCase Resource type naming must follow camel case. Path: '/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupUsageSummaries'
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L517
    R4009 - RequiredReadOnlySystemData The response of operation:'BackupResourceStorageConfigsNonCRR_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L22
    R4009 - RequiredReadOnlySystemData The response of operation:'BackupResourceStorageConfigsNonCRR_Update' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L65
    R4009 - RequiredReadOnlySystemData The response of operation:'ProtectionIntent_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L300
    R4009 - RequiredReadOnlySystemData The response of operation:'ProtectionIntent_CreateOrUpdate' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L351
    R4009 - RequiredReadOnlySystemData The response of operation:'BackupResourceVaultConfigs_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L609
    R4009 - RequiredReadOnlySystemData The response of operation:'BackupResourceVaultConfigs_Update' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L652
    R4009 - RequiredReadOnlySystemData The response of operation:'BackupResourceVaultConfigs_Put' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L704
    R4009 - RequiredReadOnlySystemData The response of operation:'BackupResourceEncryptionConfigs_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L758
    R4009 - RequiredReadOnlySystemData The response of operation:'PrivateEndpointConnection_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L852
    R4009 - RequiredReadOnlySystemData The response of operation:'PrivateEndpointConnection_Put' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L902
    R4009 - RequiredReadOnlySystemData The response of operation:'ProtectedItems_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L1298
    R4009 - RequiredReadOnlySystemData The response of operation:'ProtectedItems_CreateOrUpdate' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L1373
    R4009 - RequiredReadOnlySystemData The response of operation:'ProtectedItemOperationResults_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L1521
    R4009 - RequiredReadOnlySystemData The response of operation:'RecoveryPoints_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L1677
    R4009 - RequiredReadOnlySystemData The response of operation:'ProtectionPolicies_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L1907
    R4009 - RequiredReadOnlySystemData The response of operation:'ProtectionPolicies_CreateOrUpdate' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L1960
    R4009 - RequiredReadOnlySystemData The response of operation:'ProtectionPolicyOperationResults_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L2093
    R4009 - RequiredReadOnlySystemData The response of operation:'JobDetails_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L2221
    R4009 - RequiredReadOnlySystemData The response of operation:'BackupEngines_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L2834
    R4009 - RequiredReadOnlySystemData The response of operation:'ProtectionContainers_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L3022
    R4009 - RequiredReadOnlySystemData The response of operation:'ProtectionContainers_Register' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L3079
    R4009 - RequiredReadOnlySystemData The response of operation:'ProtectionContainerOperationResults_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L3352
    R4009 - RequiredReadOnlySystemData The response of operation:'ResourceGuardProxy_Get' is defined without 'systemData'. Consider adding the systemData to the response.
    Location: Microsoft.RecoveryServices/stable/2021-12-01/bms.json#L4313
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️~[Staging] ApiReadinessCheck succeeded [Detail] [Expand]
    ️️✔️ModelValidation succeeded [Detail] [Expand]
    Validation passes for ModelValidation.
    ️️✔️SemanticValidation succeeded [Detail] [Expand]
    Validation passes for SemanticValidation.
    ️️✔️Cross-Version Breaking Changes succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️️✔️SDK Track2 Validation succeeded [Detail] [Expand]
    Validation passes for SDKTrack2Validation

    ️️✔️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).
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Jan 26, 2022

    Swagger Generation Artifacts

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

    Breaking Changes Tracking

    ️✔️azure-sdk-for-go-track2 - armrecoveryservicesbackup - 0.4.0
    ️✔️azure-sdk-for-python-track2 - track2_azure-mgmt-recoveryservicesbackup - 4.1.1
    azure-sdk-for-go - recoveryservices/mgmt/2021-07-01/backup - v62.1.0
    azure-sdk-for-go - recoveryservices/mgmt/2021-01-01/backup - v62.1.0
    ️✔️azure-sdk-for-go - recoveryservices/mgmt/2020-12-01/backup - v62.1.0
    azure-sdk-for-go - recoveryservices/mgmt/2020-02-02/backup - v62.1.0
    azure-sdk-for-go - recoveryservices/mgmt/2019-06-15/backup - v62.1.0
    azure-sdk-for-go - recoveryservices/mgmt/2019-05-13/backup - v62.1.0
    ️✔️azure-sdk-for-go - recoveryservices/mgmt/2017-07-01/backup - v62.1.0
    ️✔️azure-sdk-for-go - recoveryservices/mgmt/2016-12-01/backup - v62.1.0
    ️✔️azure-sdk-for-go - recoveryservices/mgmt/2016-06-01/backup - v62.1.0
    azure-sdk-for-go - recoveryservices/mgmt/2021-12-01/backup - v62.1.0
    +	Const `ContainerTypeBasicProtectionContainerContainerTypeIaaSVMContainer` has been removed
    ️️✔️ azure-sdk-for-net succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from d4881f6. SDK Automation 14.0.0
      warn	Skip initScript due to not configured
      command	sudo apt-get install -y dotnet-sdk-6.0
      command	autorest --version=2.0.4421 --csharp --reflect-api-versions --license-header=MICROSOFT_MIT_NO_VERSION --use=@microsoft.azure/autorest.csharp@2.3.82 --csharp-sdks-folder=/home/vsts/work/1/s/azure-sdk-for-net/sdk ../azure-rest-api-specs/specification/recoveryservicesbackup/resource-manager/readme.md
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
      cmderr	[Autorest] realpath(): Permission denied
    • ️✔️Microsoft.Azure.Management.RecoveryServices.Backup [View full logs]  [Release SDK Changes]
    ️⚠️ azure-sdk-for-python-track2 warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from d4881f6. 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! 8.3.1 -> 8.5.4
      cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.5.4>
      cmderr	[automation_generate.sh] npm notice Run `npm install -g npm@8.5.4` to update!
      cmderr	[automation_generate.sh] npm notice
    • ️✔️track2_azure-mgmt-recoveryservicesbackup [View full logs]  [Release SDK Changes]
      info	[Changelog] **Features**
      info	[Changelog]
      info	[Changelog]   - Model AzureIaaSVMProtectionPolicy has a new parameter tiering_policy
      info	[Changelog]   - Model SubProtectionPolicy has a new parameter tiering_policy
    ️️✔️ azure-sdk-for-java succeeded [Detail] [Expand]
    ️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from d4881f6. SDK Automation 14.0.0
      command	sh ./eng/initScript.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
      command	generator automation ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
    • ️✔️recoveryservices/mgmt/2021-12-01/backup [View full logs]  [Release SDK Changes]
      Only show 12 items here, please refer to log for details.
      info	[Changelog] - New function `SubProtectionPolicy.MarshalJSON() ([]byte, error)`
      info	[Changelog] - New struct `TieringPolicy`
      info	[Changelog] - New field `OldestRecoveryPointInArchive` in struct `AzureIaaSVMProtectedItemExtendedInfo`
      info	[Changelog] - New field `NewestRecoveryPointInArchive` in struct `AzureIaaSVMProtectedItemExtendedInfo`
      info	[Changelog] - New field `OldestRecoveryPointInVault` in struct `AzureIaaSVMProtectedItemExtendedInfo`
      info	[Changelog] - New field `TieringPolicy` in struct `SubProtectionPolicy`
      info	[Changelog] - New field `OldestRecoveryPointInVault` in struct `AzureVMWorkloadProtectedItemExtendedInfo`
      info	[Changelog] - New field `OldestRecoveryPointInArchive` in struct `AzureVMWorkloadProtectedItemExtendedInfo`
      info	[Changelog] - New field `NewestRecoveryPointInArchive` in struct `AzureVMWorkloadProtectedItemExtendedInfo`
      info	[Changelog] - New field `TieringPolicy` in struct `AzureIaaSVMProtectionPolicy`
      info	[Changelog]
      info	[Changelog] Total 1 breaking change(s), 13 additive change(s).
    • ️✔️recoveryservices/mgmt/2021-07-01/backup [View full logs
      Only show 12 items here, please refer to log for details.
      info	[Changelog] - Struct `CrrJobsClient` has been removed
      info	[Changelog] - Struct `CrrOperationResultsClient` has been removed
      info	[Changelog] - Struct `CrrOperationStatusClient` has been removed
      info	[Changelog] - Struct `OperationStatusRecoveryPointExtendedInfo` has been removed
      info	[Changelog] - Struct `ProtectedItemsCrrClient` has been removed
      info	[Changelog] - Struct `RecoveryPointsCrrClient` has been removed
      info	[Changelog] - Struct `ResourceStorageConfigsClient` has been removed
      info	[Changelog] - Struct `UsageSummariesCRRClient` has been removed
      info	[Changelog] - Struct `WorkloadCrrAccessToken` has been removed
      info	[Changelog] - Field `HealthStatus` of struct `AzureFileshareProtectedItem` has been removed
      info	[Changelog]
      info	[Changelog] Total 154 breaking change(s), 0 additive change(s).
    • ️✔️recoveryservices/mgmt/2021-01-01/backup [View full logs
      Only show 12 items here, please refer to log for details.
      info	[Changelog] - Field `TargetVirtualMachineID` of struct `AzureWorkloadRestoreRequest` has been removed
      info	[Changelog] - Field `TargetVirtualMachineID` of struct `AzureWorkloadSQLRestoreWithRehydrateRequest` has been removed
      info	[Changelog]
      info	[Changelog] ### Features Added
      info	[Changelog]
      info	[Changelog] - New const `TypeIncremental`
      info	[Changelog] - New const `TypeCopyOnlyFull`
      info	[Changelog] - New const `TypeDifferential`
      info	[Changelog] - New const `TypeLog`
      info	[Changelog] - New const `TypeFull`
      info	[Changelog]
      info	[Changelog] Total 427 breaking change(s), 5 additive change(s).
    • ️✔️recoveryservices/mgmt/2020-12-01/backup [View full logs
      info	[Changelog] This is a new package
      info	[Changelog]
    • ️✔️recoveryservices/mgmt/2020-02-02/backup [View full logs
      Only show 12 items here, please refer to log for details.
      info	[Changelog] - Struct `WorkloadProtectableItemResourceListPage` has been removed
      info	[Changelog] - Struct `YearlyRetentionSchedule` has been removed
      info	[Changelog] - Field `Properties` of struct `OperationStatus` has been removed
      info	[Changelog]
      info	[Changelog] ### Features Added
      info	[Changelog]
      info	[Changelog] - New const `Failed`
      info	[Changelog] - New const `Succeeded`
      info	[Changelog] - New const `InProgress`
      info	[Changelog] - New const `Canceled`
      info	[Changelog]
      info	[Changelog] Total 3019 breaking change(s), 4 additive change(s).
    • ️✔️recoveryservices/mgmt/2019-06-15/backup [View full logs
      Only show 12 items here, please refer to log for details.
      info	[Changelog] - Struct `WorkloadProtectableItemResourceList` has been removed
      info	[Changelog] - Struct `WorkloadProtectableItemResourceListIterator` has been removed
      info	[Changelog] - Struct `WorkloadProtectableItemResourceListPage` has been removed
      info	[Changelog]
      info	[Changelog] ### Features Added
      info	[Changelog]
      info	[Changelog] - New const `Skip`
      info	[Changelog] - New const `FailOnConflict`
      info	[Changelog] - New const `CreateCopy`
      info	[Changelog] - New const `Overwrite`
      info	[Changelog]
      info	[Changelog] Total 1454 breaking change(s), 4 additive change(s).
    • ️✔️recoveryservices/mgmt/2019-05-13/backup [View full logs
      Only show 12 items here, please refer to log for details.
      info	[Changelog] - Struct `WorkloadProtectableItemResourceList` has been removed
      info	[Changelog] - Struct `WorkloadProtectableItemResourceListIterator` has been removed
      info	[Changelog] - Struct `WorkloadProtectableItemResourceListPage` has been removed
      info	[Changelog]
      info	[Changelog] ### Features Added
      info	[Changelog]
      info	[Changelog] - New const `Skip`
      info	[Changelog] - New const `Overwrite`
      info	[Changelog] - New const `FailOnConflict`
      info	[Changelog] - New const `CreateCopy`
      info	[Changelog]
      info	[Changelog] Total 1456 breaking change(s), 4 additive change(s).
    • ️✔️recoveryservices/mgmt/2017-07-01/backup [View full logs
      info	[Changelog] This is a new package
      info	[Changelog]
    • ️✔️recoveryservices/mgmt/2016-12-01/backup [View full logs
      info	[Changelog] ### Other Changes
      info	[Changelog]
      info	[Changelog] Total 0 breaking change(s), 0 additive change(s).
    • ️✔️recoveryservices/mgmt/2016-06-01/backup [View full logs
      info	[Changelog] ### Other Changes
      info	[Changelog]
      info	[Changelog] Total 0 breaking change(s), 0 additive change(s).
    ️️✔️ azure-sdk-for-go-track2 succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from d4881f6. 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
    • ️✔️armrecoveryservicesbackup [View full logs]  [Release SDK Changes]
      info	[Changelog] ### Features Added
      info	[Changelog]
      info	[Changelog] - New const `TieringModeTierAfter`
      info	[Changelog] - New const `TieringModeTierRecommended`
      info	[Changelog] - New const `TieringModeInvalid`
      info	[Changelog] - New const `TieringModeDoNotTier`
      info	[Changelog] - New function `TieringMode.ToPtr() *TieringMode`
      info	[Changelog] - New function `PossibleTieringModeValues() []TieringMode`
      info	[Changelog] - New struct `TieringPolicy`
      info	[Changelog] - New field `TieringPolicy` in struct `SubProtectionPolicy`
      info	[Changelog] - New field `TieringPolicy` in struct `AzureIaaSVMProtectionPolicy`
      info	[Changelog] - New field `OldestRecoveryPointInArchive` in struct `AzureVMWorkloadProtectedItemExtendedInfo`
      info	[Changelog] - New field `OldestRecoveryPointInVault` in struct `AzureVMWorkloadProtectedItemExtendedInfo`
      info	[Changelog] - New field `NewestRecoveryPointInArchive` in struct `AzureVMWorkloadProtectedItemExtendedInfo`
      info	[Changelog] - New field `OldestRecoveryPointInVault` in struct `AzureIaaSVMProtectedItemExtendedInfo`
      info	[Changelog] - New field `NewestRecoveryPointInArchive` in struct `AzureIaaSVMProtectedItemExtendedInfo`
      info	[Changelog] - New field `OldestRecoveryPointInArchive` in struct `AzureIaaSVMProtectedItemExtendedInfo`
      info	[Changelog]
      info	[Changelog] Total 0 breaking change(s), 12 additive change(s).
    ️⚠️ azure-sdk-for-js warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from d4881f6. 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
      cmderr	[automation_init.sh] deprecated read-package-tree@5.1.6: The functionality that this package provided is now in @npmcli/arborist
      cmderr	[automation_init.sh] deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
      cmderr	[automation_init.sh] npm WARN deprecated @opentelemetry/types@0.2.0: Package renamed to @opentelemetry/api, see https://github.com/open-telemetry/opentelemetry-js
      cmderr	[automation_init.sh] notice created a lockfile as package-lock.json. You should commit this file.
      cmderr	[automation_init.sh]  @octokit/plugin-request-log@1.0.4 requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.
      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-recoveryservicesbackup [View full logs]  [Release SDK Changes]
      info	[Changelog] **Features**
      info	[Changelog]
      info	[Changelog]   - Added Interface TieringPolicy
      info	[Changelog]   - Added Type Alias TieringMode
      info	[Changelog]   - Interface AzureIaaSVMProtectedItemExtendedInfo has a new optional parameter newestRecoveryPointInArchive
      info	[Changelog]   - Interface AzureIaaSVMProtectedItemExtendedInfo has a new optional parameter oldestRecoveryPointInArchive
      info	[Changelog]   - Interface AzureIaaSVMProtectedItemExtendedInfo has a new optional parameter oldestRecoveryPointInVault
      info	[Changelog]   - Interface AzureVmWorkloadProtectedItemExtendedInfo has a new optional parameter newestRecoveryPointInArchive
      info	[Changelog]   - Interface AzureVmWorkloadProtectedItemExtendedInfo has a new optional parameter oldestRecoveryPointInArchive
      info	[Changelog]   - Interface AzureVmWorkloadProtectedItemExtendedInfo has a new optional parameter oldestRecoveryPointInVault
      info	[Changelog]   - Interface SubProtectionPolicy has a new optional parameter tieringPolicy
      info	[Changelog]   - Added Enum KnownTieringMode
      error	breakingChangeTracking is enabled, but version or changelogItem is not found in output.
    ️⚠️ azure-resource-manager-schemas warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from d4881f6. 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] 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
    • ️✔️recoveryservicesbackup [View full logs]  [Release Schema Changes]
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-workflow-bot openapi-workflow-bot bot added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Jan 26, 2022
    @openapi-workflow-bot
    Copy link

    Hi, @anjorsh your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com).

    @openapi-workflow-bot
    Copy link

    NewApiVersionRequired reason:

    A service’s API is a contract with customers and is represented by using the api-version query parameter. Changes such as adding an optional property to a request/response or introducing a new operation is a change to the service’s contract and therefore requires a new api-version value. This is critically important for documentation, client libraries, and customer support.

    EXAMPLE: if a customer calls a service in the public cloud using api-version=2020-07-27, the new property or operation may exist but if they call the service in a government cloud, air-gapped cloud, or Azure Stack Hub cloud using the same api-version, the property or operation may not exist. Because there is no clear relationship between the service api-version and the new property/operation, customers can’t trust the documentation and Azure customer have difficulty helping customers diagnose issues. In addition, each client library version documents the service version it supports. When an optional property or new operation is added to a service and its Swagger, new client libraries must be produced to expose this functionality to customers. Without updating the api-version, it is unclear to customers which version of a client library supports these new features.

    @openapi-workflow-bot
    Copy link

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

    @anjorsh
    Copy link
    Member Author

    anjorsh commented Jan 26, 2022

    These changes for version 2021-12-01 were missed in an earlier PR for introducing this version:
    #17271

    This is not a breaking change since there are currently no users for this API version.

    "tieringPolicy": {
    "description": "Tiering policy to automatically move RPs to another tier\r\nKey is Target Tier, defined in RecoveryPointTierType enum.\r\nTiering policy specifies the criteria to move RP to the target tier.",
    "type": "object",
    "additionalProperties": {
    Copy link
    Member

    @mentat9 mentat9 Jan 28, 2022

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    additionalProperties

    Why is this modeled as additionalProperties? ARM doesn't allow additionalProperties unless the members are unknown, dynamic or user defined. Ref: https://armwiki.azurewebsites.net/api_contracts/guidelines/openapi.html#oapi032-only-use-additionalproperties-when-the-object-properties-are-dynamic-unknown-or-user-defined #Closed

    Copy link
    Member Author

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    The tieringPolicy field is a dictionary. As per the OpenAPI specification, dictionaries need to be defined with the additionalProperties keyword.
    Ref: https://swagger.io/docs/specification/data-models/dictionaries/

    Copy link
    Member

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Is the size of the dictionary dynamic? Meaning can the user only specify one element out of all the possible elements?

    Copy link
    Member Author

    @anjorsh anjorsh Feb 14, 2022

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Yes

    @mentat9 mentat9 added ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jan 28, 2022
    @mentat9
    Copy link
    Member

    mentat9 commented Jan 29, 2022

    @anjorsh, please add the WaitForARMFeedback or WaitForARMRevisit label when you are ready for revisit: that will notify the current oncall that your PR is ready for revisit.

    @openapi-workflow-bot
    Copy link

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

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

    raych1 commented Mar 7, 2022

    @anjorsh , please fix CI check failures.

    @raych1 raych1 merged commit d4881f6 into Azure:main Mar 11, 2022
    FredericHeem pushed a commit to grucloud/azure-rest-api-specs that referenced this pull request May 16, 2022
    …crosoft.RecoveryServices version 2021-12-01 (Azure#17517)
    
    * Additional TieringPolicy and ProtectedItemExtendedInfo details for version 2021-12-01
    
    * Prettier Fix
    
    * Fixing ModelValidation
    
    * Fixing LintDiff
    
    * Added more details in description as per review comments
    
    * Updated description for oldestRecoveryPoint
    
    * Fixing Prettier
    
    * Test Fix for SDK generation
    
    * SemanticValidation Fixes
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review CI-FixRequiredOnFailure
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    5 participants