[Network] Upgrade to 2025-09-01 API - SDK regen + NSP.Autorest regen - #29992
Open
santoshgh317 wants to merge 3 commits into
Open
[Network] Upgrade to 2025-09-01 API - SDK regen + NSP.Autorest regen#29992santoshgh317 wants to merge 3 commits into
santoshgh317 wants to merge 3 commits into
Conversation
- Bumped Network.Management.Sdk README to spec commit a48bb3329f0d841f42232e6f0086b6e43bc242ef, api-version 2025-09-01. - Added firstPartyServiceTag.json to the input-file list; regenerated Network.Management.Sdk against the new spec. - Bumped NetworkSecurityPerimeter.Autorest README to the same spec commit; regenerated NSP.Autorest cmdlets. - Fixed AutoRest directives: the "Common." prefix was dropped from SubResourceModel and SubResource keys in 2025-09-01 common.json, so the existing directives ($.definitions["Common.SubResourceModel"] and $.definitions["Common.SubResource"]) were silently no-ops. The directives are retargeted to the un-prefixed keys so SubResourceModel correctly inherits from SubResource. - Added ChangeLog entry under Upcoming Release.
Contributor
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Member
|
/azp run |
Contributor
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
The previous commit's regen inadvertently deleted src/Network/NetworkSecurityPerimeter.Autorest/generate-info.json, which caused CI's Get-OutdatedSubModule to hard-fail with 'generate-info.json was not found!'. Re-create it with a new generate_Id GUID. This differs from the archived id in generated/Network/NetworkSecurityPerimeter.Autorest/generate-info.json, so CI will treat the submodule as outdated and re-run autorest against the updated README (a48bb332 / 2025-09-01).
Member
|
/azp run |
Contributor
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
…tewayGlobalConfiguration The 2025-09-01 SDK regen added DisableDefaultServerHeaderInResponse to ApplicationGatewayGlobalConfiguration. AutoMapper is configured with strict destination-member validation, so any new SDK property must be mirrored on the corresponding PS wrapper or every ApplicationGateway cmdlet path throws at map time. This unblocks the 18 failing ApplicationGateway scenario tests observed on the PR CI.
Member
|
/azp run |
Contributor
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[Network] Upgrade to 2025-09-01 API - SDK regen + NSP.Autorest regen
Description
Upgrades the Network module from api-version 2025-07-01 to 2025-09-01 (spec commit
a48bb332).Changes
src/Network/Network.Management.Sdk/README.mdto the new spec commit and api-version.firstPartyServiceTag.jsonto the input-file list.Network.Management.Sdkagainst the new spec.src/Network/NetworkSecurityPerimeter.Autorest/README.mdto the same commit and regenerated NSP.Autorest cmdlets.Common.prefix fromSubResourceModelandSubResourcekeys incommon.json, so the existing directives$.definitions["Common.SubResourceModel"]and$.definitions["Common.SubResource"]had silently become no-ops. Retargeted them to the un-prefixed keys soSubResourceModelcorrectly inherits fromSubResource.Upcoming Release.Description of the change
Regeneration only - no hand-written cmdlet changes.
Testing
dotnet msbuild build.proj /p:Scope=Network-> 0 errors, 0 warnings.dotnet msbuild build.proj /t:StaticAnalysis /p:Scope=Network-> Az.Network-specific findings clean (0 breaking-change issues for Network, 18 pre-existing severity-2ConfirmImpactcosmetics on generated NSPGet-*cmdlets - same class as prior NSP regens).Checklist
ChangeLog.mdupdated under## Upcoming Releaseinsrc/Network/Network/ChangeLog.mdrelease-network-2025-09-01