-
Notifications
You must be signed in to change notification settings - Fork 193
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 Endpoint Middleware #188
Conversation
This commit builds on the work of previous `Endpoint` work to incorporate AWS-specific endpoint abstractions.
@@ -50,7 +50,7 @@ impl Credentials { | |||
session_token, | |||
expires_after: None, | |||
|
|||
provider_name: STATIC_CREDENTIALS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
formatting only. the CI format gate isn't set up for the aws runtime yet.
@@ -3,13 +3,13 @@ | |||
* SPDX-License-Identifier: Apache-2.0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
formatting only
} | ||
} | ||
|
||
type AwsEndpointProvider = Arc<dyn ResolveAwsEndpoint>; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question
I see the term resolver
used in some places and provider
in others. Is this intentional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, good catch. Halfway through I was looking at your doc and decided I liked Resolver better since it was a bit more descriptive
Issue #, if available: #109
Description of changes: Add AWS-specific endpoint support and middleware
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.