Release redisenterprise microsoft.cache 2025 04 01

[koderjoker]

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.

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).
• Other, please clarify:
  • edit this with your clarification

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 confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
• 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

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 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.

[openapi-pipeline-app]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This is the public specs repo main branch which is not intended for iterative development.
  You must acknowledge that you understand that after this PR is merged, you won't be able to stop your changes from being published to Azure customers.
  If this is what you intend, add PublishToCustomers label to your PR.
  Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
• ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
  This PR has ARMChangesRequested label. Please address or respond to feedback from the ARM API reviewer.
  When you are ready to continue the ARM API review, please remove the ARMChangesRequested label.
  Automation should then add WaitForARMFeedback label.
  ❗If you don't have permissions to remove the label, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories.
  For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  
• ❌ The required check named 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 guide

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/redisenterprise/armredisenterprise	https://apiview.dev/Assemblies/Review/11a39c9126d14e2cafeab08f37e972c1?revisionId=554fbc930bf4409d9be2de585dbf1b88
Java	azure-resourcemanager-redisenterprise	https://apiview.dev/Assemblies/Review/922e5e853b1844cda8068a39fa4a5805?revisionId=5ddf4abe83fb4e6e864dc8b9af691875
JavaScript	@azure/arm-redisenterprisecache	https://apiview.dev/Assemblies/Review/8520553c701f4efca808faa010297808?revisionId=e10f95ba9465430188f3d0e25a048a98
Python	azure-mgmt-redisenterprise	https://apiview.dev/Assemblies/Review/b90bdd2e141f4b7094949eb953899ac6?revisionId=0250dc347d624a818987225f5e8e6096
.Net	Azure.ResourceManager.RedisEnterprise	https://apiview.dev/Assemblies/Review/519be863e4414804b6d539189357aa74?revisionId=ea5b998579d842098b92a24709c51aa5

[azure-sdk]

API change check

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

Microsoft.Cache

[rkmanda]

I am closing the PR.. please open PRs when you are actually ready instead of creating placeholders to get ahead of the queue.

[koderjoker]

@rkmanda the purpose of this PR and adding the NotReadyForReview label was to give other dev owners on my team, merging into this branch, an easy way to track the release branch and combined changes getting merged into main, and get immediate feedback by having automated tests run for their changes. I had done this in the past for our api version 2023-08-01 without facing any issues.

I was not aware doing the above would get this PR ahead in the review queue, and definitely had no intention of doing so. Seeing that this PR has been closed, I assume that the label is not for this purpose and having a PR in a draft state would also impact the review order.

Was planning to close this PR anyways due to a change in release plan. I will take your suggestions into consideration when creating a new branch, and apologize for the disruption to the review process. Thank you.