redisenterprise release new api version 2025-07-01 #28675
Conversation
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this comment.
Pull Request Overview
This pull request updates the Azure Redis Enterprise Cache module to use the new stable API version 2025-07-01, moving from the previous preview version 2025-05-01-preview. The update includes regenerated documentation and code files to reflect the new API version.
Key changes include:
- Updated API version references from preview (2025-05-01-preview) to stable (2025-07-01)
- Added new
PublicNetworkAccessparameter to the Update-AzRedisEnterpriseCache cmdlet - Updated assembly version from 1.4.1 to 1.5.0
Reviewed Changes
Copilot reviewed 26 out of 26 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| generate-info.json | Updated generation ID for the new API version |
| README.md | Changed input file path from preview to stable API version and updated commit hash |
| Properties/AssemblyInfo.cs | Bumped assembly version from 1.4.1 to 1.5.0 |
| docs/*.md | Updated API model references from Api20250501Preview to Api20250701 namespace |
| custom/*.ps1 | Updated PowerShell cmdlets with new API model references and added PublicNetworkAccess parameter |
| custom/Cluster.cs | Updated namespace from preview to stable API version |
| ### -PublicNetworkAccess | ||
| Whether or not public network traffic can access the Redis cluster. | ||
| Only 'Enabled' or 'Disabled' can be set. | ||
| null is returned only for clusters created using an old API version which do not have this property and cannot be set. |
There was a problem hiding this comment.
The documentation for the PublicNetworkAccess parameter contains a formatting issue. The word 'null' should be formatted as code using backticks for consistency with PowerShell documentation standards.
| null is returned only for clusters created using an old API version which do not have this property and cannot be set. | |
| `null` is returned only for clusters created using an old API version which do not have this property and cannot be set. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. |
|
@isra-fel addressed the comments, please review |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
2 participants
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.