fix: container test should not run app vulns scan by default #1445
Conversation
This file contains 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
ghost
requested review from
ahmed-agabani-snyk
force-pushed
the
feat/app-vulns-parameter-2
branch
from
a84e627
to
b62c1c0
Compare
|
Expected release notes (by @ahmed-agabani-snyk) fixes:
|
JackuB
approved these changes
Oct 6, 2020
anthogez
approved these changes
Oct 6, 2020
|
🎉 This PR is included in version 1.410.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This was referenced Jan 17, 2022
This was referenced Apr 21, 2023
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.
What does this PR do?
removes containers test default
--app-vulnsscanHow should this be manually tested?
snyk container test mladkau/snykinAny background context you want to provide?
Slack Thread
What are the relevant tickets?
DC-852