Repository navigation
Add support for private link client in v2 - #30303
srinivaas-ganesan wants to merge 3 commits into
Conversation
|
Azure Pipelines: Successfully started running 2 pipeline(s). There may be pipelines that require an authorized user to comment /azp run to run. |
|
Thank you for your contribution srinivaas-ganesan! We will review the pull request and get back to you soon. |
There was a problem hiding this comment.
🟢 Approval recommended
Static review found no blocking issues in this narrowly scoped update; tests were not executed.
No open issues 🎉
What changed in this PR
Updates Az.Network’s common Private Link cmdlets for Data Replication vaults to API version 2026-05-01.
Changes:
- Updates the provider API version while preserving capability flags.
- Adds regression tests for configuration lookup and parameter availability.
- Documents the update in module and repository release notes.
| File | Description |
|---|---|
| src/Network/Network/PrivateLinkService/PrivateLinkServiceProvider/ProviderConfiguration.cs | Updates the Data Replication API version. |
| src/Network/Network/ChangeLog.md | Adds module release notes. |
| src/Network/Network.Test/UnitTests/PrivateLinkProviderConfigurationTests.cs | Tests version, capabilities, case-insensitive lookup, and parameter availability. |
| ChangeLog.md | Adds repository release notes. |
Review effort: Balanced
|
/azp run |
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
NoriZC
added
Request X Engineering Agent
X Engineering Agent ReportReview — Comments No confirmed semantic findings. The DataReplication-only API update reaches the existing connection and private-link resource operations consistently. The added author tests detect an incorrect API version and check case-insensitive lookup, capability flags and parameter inclusion. Upcoming-release notes match the change. Upstream CI is green. The author tests were inspected, not executed by this Agent; HTTP response compatibility and sovereign-cloud API availability remain unverified. Test validation
Risk assessment — 26/100 · MediumThe Medium rating is driven by security-sensitive behavior.
Posted by x-engineering-agent (Reviewer) |
|
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. |
![x-engineering-agent[bot]](https://avatars.githubusercontent.com/in/4205534?s=60&v=4){kind=small}
There was a problem hiding this comment.
srinivaas-ganesan Ready for human review. See the X Engineering Agent Report.
x-engineering-agent
Bot
added
X Engineering Agent Reviewed
|
/azp run |
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
🤖 PR Validation —⚠️ Review suggested
️✔️Az.Accounts
️✔️Az.ApplicationInsights
️✔️Az.CognitiveServices
️✔️Az.Compute
️✔️Az.Dns
️✔️Az.Maintenance
️✔️Az.ManagedServiceIdentity
️✔️Az.Monitor
️✔️Az.OperationalInsights
️✔️Az.PrivateDns
️✔️Az.RecoveryServices
️✔️Az.ResourceGraph
️✔️Az.Resources
️✔️Az.Security
️✔️Az.ServiceBus
️✔️Az.Sql
️✔️Az.Storage
️✔️Az.Websites
Description
Microsoft.DataReplication API version 2024-09-01 was earlier onboarded to PE. In this PR we are updating the version to 2026-05-01
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.