Add PSM entry to example nuget.config #3508
Conversation
Added package source mapping for specific package sources.
|
Learn Build status updates of commit d1865ff: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
There was a problem hiding this comment.
Pull Request Overview
This PR adds Package Source Mapping (PSM) configuration to the example nuget.config file, demonstrating how to enforce that certain packages only come from specific package sources.
Key Changes
- Added a
packageSourceMappingsection to the example configuration showing how to map package patterns to specific sources - Demonstrates mapping ES.* packages to "MyRepo - ES" source and all other packages to the official NuGet source
donnie-msft
left a comment
donnie-msft
left a comment
There was a problem hiding this comment.
Glad to see that these examples are being referenced to customers and thank you for updating this one!
One problem we see is customers not following the best-practice of clearing sections, so I've recommended we add that for package source mapping example in your update.
|
@baronfel do you mind addressing the comments? |
Co-authored-by: Donnie Goodson <[email protected]>
Co-authored-by: Copilot <[email protected]>
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 84ae399: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 88b6cd6: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
Added package source mapping for specific package sources.
I often reference this example config and was surprised to not see PSM config in it.