Skip to content

error codes for awsQuery protocol don't match error structure name #65

@kmitchener

Description

@kmitchener

Raw error code response from AWS uses <Code> element such as "NoSuchEntity" which doesn't match what we're extracting as the error type "NoSuchEntityException".

<ErrorResponse xmlns="https://iam.amazonaws.com/doc/2010-05-08/">
  <Error>
    <Type>Sender</Type>
    <Code>NoSuchEntity</Code>
    <Message>The user with name itty-aws-test-user cannot be found.</Message>
  </Error>
  <RequestId>67c5e7e6-8119-4205-8d38-db0207d2c420</RequestId>
</ErrorResponse>

Smithy model:

    "com.amazonaws.iam#NoSuchEntityException": {
      "type": "structure",
      "members": {
        "message": {
          "target": "com.amazonaws.iam#noSuchEntityMessage"
        }
      },
      "traits": {
        "aws.protocols#awsQueryError": {
          "code": "NoSuchEntity",
          "httpResponseCode": 404
        },
        "smithy.api#documentation": "<p>The request was rejected because it referenced a resource entity that does not exist. The\n      error message describes the resource.</p>",
        "smithy.api#error": "client",
        "smithy.api#httpError": 404
      }
    },

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions