feat: update cli-extension-os-flows for Closed Beta. - #6081
Merged
Conversation
- adds Risk Score to Open Source test if feature flags are present
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) ✅ code/snyk check is complete. No issues have been found. (View Details) |
cmars
approved these changes
Jul 31, 2025
bsalomon-snyk
marked this pull request as ready for review
July 31, 2025 19:11
PeterSchafer
approved these changes
Jul 31, 2025
Contributor
|
Suggestion: At some point we might want to add some happy path User Journey tests for Risk score. You might even be able to re-use some of the existing tests in |
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.
Pull Request Submission Checklist
are release-note ready, emphasizing
what was changed, not how.
What does this PR do?
Adds risk score to the JSON and human readable CLI output of the Open Source Test for users with these feature flags enabled.
Where should the reviewer start?
Testing that existing features are unaffected. Users opting in to closed beta/testers can verify presence of risk score on test findings.
How should this be manually tested?
Please see documentation at https://docs-preview.snyk.io/9UspT11TEeR92StpZv8B/risk-score-in-cli
What's the product update that needs to be communicated to CLI users?
There are no changes for customers who are not opted in.
Risk assessment (Low | Medium | High)?
Low - closed beta behind feature flags
Any background context you want to provide?
Adds risk score to Open Source Test for select customers