Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws/session: Fix client init not exposing endpoint resolve error #3059

Merged
merged 2 commits into from
Jan 2, 2020

Conversation

jasdel
Copy link
Contributor

@jasdel jasdel commented Dec 31, 2019

Fixes the SDK API clients not surfacing endpoint resolution errors, when the EndpointResolver is unable to resolve an endpoint for the client and region.

Fixes the SDK API clients not surfacing endpoint resolution errors, when
the EndpointResolver is unable to resolve an endpoint for the client and
region.
@jasdel jasdel added the needs-review This issue or pull request needs review from a core team member. label Dec 31, 2019
@jasdel jasdel requested a review from skotambkar December 31, 2019 19:17
// was created.
return
}
r.Error = err
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be helpful to check if we need to wrap this error

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The error that will be returned will be a UnknownEndpointError error with

e.g.

UnknownEndpointError: could not resolve endpoint
	partition: "aws", service: "s3", region: "",

@jasdel jasdel removed the needs-review This issue or pull request needs review from a core team member. label Dec 31, 2019
@jasdel jasdel merged commit 81e3e85 into aws:master Jan 2, 2020
aws-sdk-go-automation pushed a commit that referenced this pull request Jan 6, 2020
===

### Service Client Updates
* `service/comprehend`: Updates service API and documentation
* `service/ec2`: Updates service API and documentation
  * This release supports service providers configuring a private DNS name for services other than AWS services and services available in the AWS marketplace. This feature allows consumers to access the service using an existing DNS name without making changes to their applications.
* `service/mediapackage`: Updates service API and documentation
  * You can now restrict direct access to AWS Elemental MediaPackage by securing requests for live content using CDN authorization. With CDN authorization, content requests require a specific HTTP header and authorization code.

### SDK Bugs
* `aws/session`: Fix client init not exposing endpoint resolve error ([#3059](#3059))
  * Fixes the SDK API clients not surfacing endpoint resolution errors, when the EndpointResolver is unable to resolve an endpoint for the client and region.
aws-sdk-go-automation added a commit that referenced this pull request Jan 6, 2020
Release v1.27.1 (2020-01-06)
===

### Service Client Updates
* `service/comprehend`: Updates service API and documentation
* `service/ec2`: Updates service API and documentation
  * This release supports service providers configuring a private DNS name for services other than AWS services and services available in the AWS marketplace. This feature allows consumers to access the service using an existing DNS name without making changes to their applications.
* `service/mediapackage`: Updates service API and documentation
  * You can now restrict direct access to AWS Elemental MediaPackage by securing requests for live content using CDN authorization. With CDN authorization, content requests require a specific HTTP header and authorization code.

### SDK Bugs
* `aws/session`: Fix client init not exposing endpoint resolve error ([#3059](#3059))
  * Fixes the SDK API clients not surfacing endpoint resolution errors, when the EndpointResolver is unable to resolve an endpoint for the client and region.
@jasdel jasdel deleted the fixup/EndpointResolveErr branch March 26, 2021 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants