-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
101 requesting automatic termination of search after x time or y results #118
101 requesting automatic termination of search after x time or y results #118
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree the limit param meets the requirements for the FR - I don't see anything significant to be gained by implementing a timeout option. The tests also need to be updated to provide coverage for this new limit
param
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added tests for coverage of the new feature. This looks ready to merge!
Changes
Created one option:
--limit
allows user to specify number of results returnedNote
After conducting tests with the
--limit
option, it was determined that there is no need to implement an additional timeout option after x amount of time. Setting a limit should effectively achieve the desired outcome. Open to making adjustments based on specific requirements or needs.Limits:
Cortex XDR: Default: 1000, Max: Default
Microsoft Defender for Endpoint: Default: 100000, Max: 100000
SentinelOne (PowerQuery): Default/Max: 1000
SentinelOne (Deep Visibility): Default/Max: 20000
VMware Carbon Black EDR: Default/Max: None
VMware Carbon Black Cloud Enterprise EDR: Default/Max: None
Note: Exceeding the maximum limits will automatically set the limit to its maximum value, where applicable.
closes #101