I’m not sure when this problem arose, and I understand that this was originally a third-party plugin, but the Crowdstrike plugin appears to have an API error now. Error in thread.
Error:
[BODY
{
"errors": [
{
"code": 400,
"message": "offset 10000 and limit 100 are invalid; offset + limit must be less than or equal to 10000"
}
],
"meta": {
"powered_by": "discover-api",
"query_time": 0.000736309,
"trace_id": "a487913c-b8e1-4958-985c-76681314bd63"
}
}
]
I can’t find in the GitHub source where these settings might have taken place, so I’m curious if it’s a bug since CQ might have ingested the plugin internally?
The issue you’re seeing is most likely happening as a result of an API request to a Crowdstrike API during the sync, and I think that’s why you can’t find it by grepping the code (that code must be in a dependency that the plugin is importing).
We don’t really do that kind of SQL in the CloudQuery SDK, but just in case, I grepped across our codebases and didn’t find anything. We haven’t ingested the plugin internally. I think the problem you found is legit, so what I would do is open an issue on their repo: Crowdstrike Issue Tracker.
We’re also in the process of developing a CloudQuery-maintained Crowdstrike plugin, which is on RC at the moment. You can try it here: Crowdstrike Plugin Documentation.
fwiw, I found that the issue is from Crowdstrike itself. Not the plugin, and of course, not CloudQuery. Thanks again for replying and offering your time to discuss this.
I guess it’ll be a word of caution for y’all as you develop your own Crowdstrike API that this is an issue that exists on their end. For some reason, they have a hard limit on paginating through 10,000 resources.