Inconsistent error handling
Opened this issue · 0 comments
niborg commented
I'm noticing that certain resource requests have different error handling. For instance, returning a 422 for a volume action will raise a FailedCreate
error, but a 429 response doesn't raise an error at all but returns a json string containing the body of the response. The code for this resource is pretty straightforward. Is there a reason for this approach?