Closed bretlowery closed 9 months ago
I suspect the Wiz API is returning an error that Steampipe is unable to handle.
Found it: if the Wiz API endpoint is set to the wrong tenant endpoint (e.g. by specifying the wrong two-digit value in the XX in https://api.usXX.app.wiz.io/graphql) this is returned. Is there any way to make that a more user-friendly error message?
Welcome to Steampipe @bretlowery and thank you so much for creating the issue with such great details 👍.
The API does return a very weird message, do we only get it if we specify the wrong two-digit values in the XX in https://api.usxx.app.wiz.io/graphql)? Are there more scenarios where we are likely to receive this error?
If it’s failing in the angle bracket, quite possibly, but not sure of specifics.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.
Apologies for the radio silence on this issue @bretlowery !!
As you mentioned, the error is returned by the Wiz API without any clear instructions on what failed. When I tamper the url
config argument, I get the following error -
select
id,
status,
severity,
created_at
from
wiz_issue
where
severity = 'CRITICAL';
Error: wiz: failed to parse token response: invalid character 'U' looking for beginning of value (SQLSTATE HV000)
+----+--------+----------+------------+
| id | status | severity | created_at |
+----+--------+----------+------------+
+----+--------+----------+------------+
Describe the bug Wiz queries return: Error: decoding response: invalid character '<' looking for beginning of value (SQLSTATE HV000)
Steampipe version (
steampipe -v
) Steampipe v0.21.1To reproduce
Error: decoding response: invalid character '<' looking for beginning of value (SQLSTATE HV000)