fix: remove public npm registry calls for network isolation compliance#3590
Closed
ramsessanchez wants to merge 2 commits intomainfrom
Closed
fix: remove public npm registry calls for network isolation compliance#3590ramsessanchez wants to merge 2 commits intomainfrom
ramsessanchez wants to merge 2 commits intomainfrom
Conversation
- Change networkIsolationPolicy from Permissive to Restricted in sdk-release.yml - Add customRegistry: useNpmrc to all Npm@1 tasks in install-tools.yml so AutoRest, AutorestCore, and Rush installs route through the private Azure Artifacts feed instead of the public npm registry Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
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.
Summary
The SDK release pipeline has been failing because outbound calls to the public npm registry (
egistry.npmjs.org) are blocked by network isolation policies.
Changes
.azure-pipelines/sdk-release.yml\
etworkIsolationPolicy\ from \Permissive\ to \Restricted\ to comply with org-level network isolation policies.
.azure-pipelines/common-templates/install-tools.yml\
Context
The \Configure-PrivateNpmFeed.ps1\ script and
pmAuthenticate@0\ steps were already correctly setting up and authenticating the private feed — the gap was that the \Npm@1\ tasks were not instructed to use it via \customRegistry: useNpmrc.