configure number of parallel scanners from the API #147
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
akpsgit
reviewed
Mar 15, 2023
akpsgit
reviewed
Mar 15, 2023
FrimIdan
changed the title
akpsgit
previously approved these changes
Mar 16, 2023
fishkerez
force-pushed
the
conf-par-scan
branch
from
17af60a
to
521d223
Compare
FrimIdan
approved these changes
Mar 16, 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.
Description
Allow the user to set the number of parallel scanning job VMs that will be running in parallel for every scan.
This is set currently only from the API (via the ScanConfig object)
Max number of scanning jobs is 20
Default value (if not set) is 2
Type of Change
[ ] Bug Fix
[ *] New Feature
[ ] Breaking Change
[ ] Refactor
[ ] Documentation
[ ] Other (please describe)
Checklist