Uploaded image for project: 'Insights Experiences'
  1. Insights Experiences
  2. HMS-743

Improve error handling of Provisioning service

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • hms-0.4
    • None
    • Provisioning
    • 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"`
      }
      

              avitova Anna Vitova
              oezr@redhat.com Ondrej Ezr
              Akhil Jha Akhil Jha
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: