Skip to content

Improved Error handling #2725

Open
Open
@vincenttran-msft

Description

@vincenttran-msft

Currently, this is the usage patterns when encountering an error:

Image
stdout:

Base error: server returned error status which will not be retried: 404
Status code: 404
Error kind: HttpResponse(NotFound, "ContainerNotFound")
Inner error kind: HttpResponse(NotFound, "ContainerNotFound")

Therefore, the two main asks to improve error handling are:

  1. Exposing the raw response (so that we can get all the information returned from the service)
  2. Ideally: A standard Azure Error deserialization model supported through Azure Core

Although there are several Storage specific errors (and thus several different forms the XML bodies can take), we are curious as to whether a standard Azure Error deserialization model would help to standardize error handling or at the very least simplify implementation for library-specific error models.
Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageWorkflow: This is a new issue that needs to be triaged to the appropriate team.

    Type

    No type

    Projects

    Status

    Untriaged

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions