-
Notifications
You must be signed in to change notification settings - Fork 4.1k
PS Release Network API Version 2025-01-01 #28692
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: Prajjwal Kamboj <[email protected]>
…ions on Vpn Gateway (#28642)
Co-authored-by: ANKUR SOOD <[email protected]> Co-authored-by: Copilot <[email protected]>
Co-authored-by: Karthik Gumpu (from Dev Box) <[email protected]>
…28685) Co-authored-by: Copilot <[email protected]>
Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the Network Security Perimeter AutoRest module to use API version 2025-01-01, replacing the previous 2024-07-01 version. The upgrade introduces new system metadata fields and additional headers in API responses, along with updated test recordings and improved service tag functionality.
Key changes:
- Updated API version from 2024-07-01 to 2025-01-01 across all Network Security Perimeter resources
- Added new systemData fields containing creation and modification metadata to API responses
- Enhanced service tag functionality by implementing previously skipped tests
Reviewed Changes
Copilot reviewed 88 out of 277 changed files in this pull request and generated no comments.
Show a summary per file
File | Description |
---|---|
README.md | Updated OpenAPI specification reference to point to 2025-01-01 version |
UX/*.json | Updated API version references in UX configuration files |
Properties/AssemblyInfo.cs | Updated assembly version from 7.16.2 to 7.21.0 |
test/*.Recording.json | Updated test recordings to reflect new API version and system metadata |
Get-AzNetworkSecurityPerimeterServiceTag.Tests.ps1 | Enabled previously skipped service tag tests |
generate-info.json | Updated generation ID |
/azp run |
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run azure-powershell - powershell-core |
/azp run azure-powershell - powershell-core |
No pipelines are associated with this pull request. |
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
@microsoft-github-policy-service rerun |
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.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.