Endpoint Resolution Upgrade Guidance #755
rcoh
announced in
Change Log
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Endpoint resolution has been overhauled to support virtual addressing, dynamic endpoint resolver generation, and parameterized endpoints.
Changes
Remove deprecated
ResolveAwsEndpoint
interfaces.In general, the path forward is to either:
endpoint_url
either onSdkConfig
,ConfigLoader
or<service>::config::Builder::endpoint_url
.The following APIs have been removed:
SdkConfig::endpoint_resolver()
: This getter referred a field that has been removed.sdk_config::Builder::set_endpoint_resolver(resolver)
: This setter has been removed.ConfigLoader::endpoint_resolver(resolver)
: This previously deprecated setter has been removed.aws-endpoint
crate:AwsEndpoint
,CredentialScope
, andResolveAwsEndpoint
.Endpoint
has been removed from generated services. Useendpoint_url
which accepts a string directly instead. Alternatively,&'static str
provides an automatic implementation ofResolveEndpoint
.Endpoint
inaws-smithy-http
has been deprecatedEndpoint
will be removed at a later date. Instead of usingEndpoint
, you can:SdkConfig::endpoint_url
or<service>::Config::endpoint_url
aws_smithy_types::Endpoint
Beta Was this translation helpful? Give feedback.
All reactions