-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
Improve error handling of Provisioning service
-
0% To Do, 0% In Progress, 100% Done
-
False
-
dev-ready, doc-ready, po-ready, qe-ready, ux-ready
Goal: Consistently inform users about what went wrong throughout API and UI.
This aims mainly on reporting what went wrong in the API, UI will read these errors and display them.
Acceptance criteria:
// ResponseError is used as a payload for all errors type ResponseError struct { // HTTP status code HTTPStatusCode int `json:"-"` // error type name Name string `json:"name"` // user facing error message Message string `json:"msg"` // trace id from context (if provided) TraceId string `json:"trace_id,omitempty"` // full root cause Error error `json:"error"` }
- relates to
-
HMS-1201 Surface human readable error messages in the frontend
- Closed