Libcloud
  1. Libcloud
  2. LIBCLOUD-114

Provider HTTP Error responses need to be propagated in a better way.

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None

      Description

      Currently when a provider returns an unexpected (error) response the response code and message must be parsed from a message string in a base Exception. Instead we should include the error code and error message in an exception class (ProviderHTTPResponseError).

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            Brian Hoenig
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - 24h
              24h
              Remaining:
              Remaining Estimate - 24h
              24h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development