Open singhabh27 opened 4 days ago
main
branch which is not intended for iterative development.PublishToCustomers
label to your PR.release-
(see aka.ms/azsdk/api-versions#release--branches).ARMReview
). This PR must get ARMSignedOff
label from an ARM reviewer.ARMChangesRequested
label. Please address or respond to feedback from the ARM API reviewer. ARMChangesRequested
label. WaitForARMFeedback
label. write access
per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories.Swagger PrettierCheck
has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guideLanguage | Package Name | ApiView Link |
---|---|---|
Go | sdk/resourcemanager/recoveryservices/armrecoveryservicesbackup | There is no API change compared with the previous version |
JavaScript | @azure/arm-recoveryservicesbackup | https://apiview.dev/Assemblies/Review/859c2af295154fe6816f57a966fd8dee?revisionId=2fdfdd505ae9465ebf4237a3ef0bb4fa |
Java | azure-resourcemanager-recoveryservicesbackup | https://apiview.dev/Assemblies/Review/a4a183e5963645238761f94a38ed47e9?revisionId=f1edc88a254447c99403baff93f4f0e6 |
.Net | Azure.ResourceManager.RecoveryServicesBackup | https://apiview.dev/Assemblies/Review/2e670a3b8b294fadbf4a793f6c6aaa28?revisionId=93cea8a347ca467982e052ded02e4087 |
Swagger | Microsoft.RecoveryServices | https://apiview.dev/Assemblies/Review/87cb55db6e9f4146a1f242e528aece8b?revisionId=644e639e3f42429ca0959feedb5d8f6d |
/azp run
@singhabh27 Perhaps I'm missing something, but I don't see any notable difference between the new version and 2024-04-01. Can you please point out the difference(s) for the new version?
@ms-bogdan-rotaru, the above PR is created for swagger completeness purpose. If we create a new API Version for any of below RP for any feature: recoveryservices, recoveryservicesbackup, recoveryservicessiterecovery, for swagger completeness, we have to make change in other 2 Repos. https://github.com/Azure/azure-rest-api-specs/pull/30681 https://github.com/Azure/azure-rest-api-specs/pull/30682 https://github.com/Azure/azure-rest-api-specs/pull/30307
ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood and followed the instructions by checking all the boxes:
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table in the `Generated ApiView` comment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the [suppressions guide](https://aka.ms/azsdk/pr-suppressions) to get approval.Getting help
Purpose of this PR
andDue diligence checklist
.write access
per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Merge
comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.queued
state, please add a comment with contents/azp run
. This should result in a new comment denoting aPR validation pipeline
has started and the checks should be updated after few minutes.