Add --dry-run flag to CLI (#1967)#2046
Open
YUVRAJ-SINGH-3178 wants to merge 2 commits into
Open
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
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.
Hey! This PR adds a handy
--dry-runflag to the CLI as requested in #1967.It makes it super easy to preview exactly what command a plugin is going to run under the hood, without actually firing off a scan or saving a task to the database.
Here's how it works:
--dry-runargument to thesecuscan scanparser incli.py.plugin_managerto build the command with all the interpolated inputs.docker runprefix (with memory/cpu limits) that theexecutorwould normally use.It's great for debugging plugins. Let me know what you think!