Skip to content

Conversation

@vikramkotturu
Copy link
Contributor

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

spec_pr_review_workflow_diagram

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

  • New resource provider.
  • New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
  • Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
  • Update existing version to fix OpenAPI spec quality issues in S360.
  • Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
  • [x ] Other, please clarify:

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:

  • [x ] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
  • [x ] I have reviewed following Resource Provider guidelines, including
    ARM resource provider contract and
    REST guidelines (estimated time: 4 hours).
    I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

Rebasing ASE Database Backup changes which were previously ARM Signed off - This PR is just rebasing the changes to support ASE Database Backup which was previously ARMSigned off after review. - URL of original PR that was ARM Signed off (based on version 2024-10-01) https://github.com/Azure/azure-rest-api-specs/assets/4429827/5bb5e7ce-8aff-4dbb-a3f8-0d9b68fef5b1 - This PR has the same changes but using the latest released version 2025-01-01 as the base.
Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

  • First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
  • If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
  • To understand what you must do next to merge this PR, see the Next 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.
  • For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
    and https://aka.ms/ci-fix.
  • For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
  • If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
    This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
  • If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Copied the files in a separate commit.
This allows reviewers to easily diff subsequent changes against the previous spec.
Updated the API version from stable/2025-01-01 to stable/2025-02-01.
@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Apr 2, 2025

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Apr 2, 2025

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

@azure-sdk
Copy link
Collaborator

azure-sdk commented Apr 2, 2025

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
Swagger Microsoft.RecoveryServices

@Azure Azure deleted a comment from azure-sdk Apr 2, 2025
@hiaga
Copy link
Member

hiaga commented Apr 3, 2025

LGTM, please add the previous PR link which was reviewed earlier and ARMSignedOff.

@hiaga hiaga added AzCoreIDC PublishToCustomers Acknowledgement the changes will be published to Azure customers. labels Apr 3, 2025
@pcsin
Copy link

pcsin commented Apr 3, 2025

The original PR link is pointing to an image. Pls update PR description with the original PR link.

Additionally wanted to understand the intent behind this change?

@openapi-pipeline-app openapi-pipeline-app bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Apr 3, 2025
@vikramkotturu
Copy link
Contributor Author

Added link for previous PR that was signed off #32849

@vikramkotturu
Copy link
Contributor Author

LGTM, please add the previous PR link which was reviewed earlier and ARMSignedOff.

#32849 used wrong link last time

@openapi-pipeline-app openapi-pipeline-app bot added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Apr 3, 2025
Copy link

@pcsin pcsin left a comment

Choose a reason for hiding this comment

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

:shipit:

@pcsin
Copy link

pcsin commented Apr 3, 2025

Signing-off, the change rebases this version on top of released stable GA version (2025-01-01)

@pcsin pcsin added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Apr 3, 2025
@openapi-pipeline-app openapi-pipeline-app bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Apr 3, 2025
@vikramkotturu vikramkotturu force-pushed the recoveryservicesbackup-stable2-2025-02-01 branch from 9472e58 to d55af30 Compare April 3, 2025 10:33
@pcsin
Copy link

pcsin commented Apr 3, 2025

Approving Avocado suppression as is done in the previous PR on which the change is based on - https://github.com/Azure/azure-rest-api-specs/pull/32231/checks?check_run_id=39827384298

Please take necessary fixes complying with Avocado automated check in subsequent iterations.

@hiaga hiaga enabled auto-merge (squash) April 3, 2025 13:32
@hiaga hiaga merged commit 49ccdfe into Azure:main Apr 4, 2025
38 of 45 checks passed
@github-actions github-actions bot added the brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. label Apr 4, 2025
v-maksymm pushed a commit that referenced this pull request Apr 8, 2025
…was ARMSigned off previously (#33661)

* Copy files from stable/2025-01-01

Copied the files in a separate commit.
This allows reviewers to easily diff subsequent changes against the previous spec.

* Update version to stable/2025-02-01

Updated the API version from stable/2025-01-01 to stable/2025-02-01.

* Added tag for 2025-02-01 in readme file

* Rebasing Sybase ASE Backup changes which were previously signed off.

* Fixed prettier issues.

* Pretttier fixes.

* correcting passive stamp version in readme.md
nwnt pushed a commit to nwnt/azure-rest-api-specs that referenced this pull request Jun 10, 2025
…was ARMSigned off previously (Azure#33661)

* Copy files from stable/2025-01-01

Copied the files in a separate commit.
This allows reviewers to easily diff subsequent changes against the previous spec.

* Update version to stable/2025-02-01

Updated the API version from stable/2025-01-01 to stable/2025-02-01.

* Added tag for 2025-02-01 in readme file

* Rebasing Sybase ASE Backup changes which were previously signed off.

* Fixed prettier issues.

* Pretttier fixes.

* correcting passive stamp version in readme.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved-Avocado ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review AzCoreIDC brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. customer-reported Issues that are reported by GitHub users external to the Azure organization. new-api-version PublishToCustomers Acknowledgement the changes will be published to Azure customers. Recovery Services Backup resource-manager

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants