Closed iargue closed 6 months ago
I've also recently encountered this issue with one of my tenants. It only happened on one or two incidents, but the 5
value seems to be completely undocumented and potentially a bug with Graph itself, rather than the SDK.
Is there someone at Microsoft I can reach out to with the alert and tenant ID to assist troubleshooting?
I get the same error when trying to get all alerts from the alerts_v2 endpoint.
Exception has occurred: Exception Invalid key: 5 for enum <enum 'EvidenceVerdict'>. KeyError: '5'
During handling of the above exception, another exception occurred:
File "/mnt/c/source/m365defender/get-m365alerts.py", line 19, in list_alerts
result = await client.security.alerts_v2.get()
File "/mnt/c/source/m365defender/get-m365alerts.py", line 22, in
Im also facing this issue
As mentioned in my comment above, I don't believe this is an SDK bug, but rather a bug in the Graph API spec.
5
is not a valid EvidenceVerdict
member in the API specifications, so Kiota is correctly raising an Exception.
It would be much appreciated if someone from MSFT could point me in the right place to submit a bug report for Graph itself.
Not sure if it is just me. But for my usecase the error is gone. Can you check again if it also works for you?
I have exactly the same pb. I saw also the issue in the Golang SDK. https://github.com/microsoftgraph/msgraph-sdk-go/issues/555. A comment states
" I don't believe this is an SDK bug, but rather a bug in the Graph API spec."
In any case, the SDK should be able to handle errors from the API. I fixed the problem with a horrible hack in kiota_serialization_json\json_parse_node.py at line 199 in order to get the alerts
try:
#hack
if camel_case_key == '5':
return enum_class['Unknown']
return enum_class[camel_case_key] # type: ignore
except KeyError:
raise Exception(f'Invalid key: {camel_case_key} for enum {enum_class}.')
When trying to expand an incident with alerts via this code:
Full traceback