test: capture valid json output with policy #5581
Closed
Conversation
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
thisislawatts
force-pushed
the
test/capture-valid-esoj-output-with-policy
branch
2 times, most recently
from
72bb996 to
85aaf21
Compare
thisislawatts
force-pushed
the
test/capture-valid-esoj-output-with-policy
branch
from
85aaf21 to
49a872f
Compare
Contributor
|
Your PR has not had any activity for 30 days. In 2 days I'll close it. Make some activity to remove this. |
Contributor
|
Your PR has now been stale for 2 days. I'm closing it. |
github-actions
bot
deleted the
test/capture-valid-esoj-output-with-policy
branch
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
What does this PR do?
Stepping back through the versions of snyk-policy the bug seems to have been introduced by adopting the vite bundler in version 3.0
Release v3.0.0 · snyk/policy
With v2.0.8, the CLI works as expected outputting valid JSON.
I have added an acceptance test for this behaviour with the CLI.
Note that the first line of stdout includes:
snyk:module [email protected] => { name: "cxct", version: "0.0.1-security" } +0msYou can get the test to pass by installing an older version of the CLI and injecting that to your tests: