[release/v7.6] Add network isolation policy parameter to vPack pipeline #26444
+15
−0
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.
Backport of #26223 to release/v7.6
Triggered by @TravisEz13 on behalf of @TravisEz13
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Impact
REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.
Tooling Impact
Optional tooling enhancement that allows build engineers to specify network isolation policies (KS4, R1, Netlock) for vPack builds. Default behavior remains unchanged (RS1). Enables more flexible build environment configuration for testing and security scenarios.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Verified by running the vPack pipeline with different network isolation policy values. The parameter is correctly propagated and used in Windows host configuration. Clean cherry-pick with no conflicts.
Risk
REQUIRED: Check exactly one box.
Medium risk: Changes CI/CD pipeline configuration to add network isolation policy support. This is a parameter addition with a safe default (RS1), so existing builds will continue working unchanged. The change has been validated in master and previously backported to v7.4 and v7.5 without issues.