-
Notifications
You must be signed in to change notification settings - Fork 103
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
No method to save search criteria for a dynamic site? #317
Comments
It looks like it's supposed to use the Do you have example criteria you are saving that doesn't work? |
I've tried several permutations, mostly using IP_ADDRESS and ASSET (name). Here's one example:
Regardless of the criteria I use, if I set site.search_criteria, the resulting POST to /api/2.1/site_configurations/ fails with a Nexpose::APIError nsc.log indicates a NullPointerException:
|
The error is not that helpful of course, but it seems like you may be using invalid criteria. Which connection type is this for? Aside from DHCP and Sonar connections most fields appear to be defined here: https://github.com/rapid7/nexpose-client/blob/master/lib/nexpose/discovery/filter.rb |
I'm using an AWS connection, so you are correct - i was using invalid criteria. That said, using the criteria identified for AWS connections in nexpose/discovery/filter.rb yields the same results. I've tried instance_name, instance_type, and instance_state to no avail. |
Documentation for Site#save indicates changes to discovery connection and asset filter must be made through an alternate method -- DiscoveryConnection#update_site -- but this method does not exist.
Site#save appears to be working correctly with a set discovery_config, but failing with any set search_criteria.
Am I missing something?
The text was updated successfully, but these errors were encountered: