-
Notifications
You must be signed in to change notification settings - Fork 638
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
update devguide for endpointsv2 #2205
Conversation
* `EndpointResolverV2` | ||
* `BaseEndpoint` | ||
|
||
## V1: `EndpointResolver` |
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: Should we move v2 to the top? Inclined to say yes given it's what we want people to use (it effectively supercedes v1 as we know).
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.
yes, i agree
## Customization | ||
|
||
There are two "versions" of endpoint resolution config within the SDK. | ||
behavior of endpoint resolution within the SDK: |
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.
prob typo: within the SDK
used twice in awkward phrasing
resolved endpoint. You can prevent the SDK from mutating your custom endpoints by setting | ||
[HostnameImmutable]({{< apiref "aws#Endpoint.HostnameImmutable" >}}) to`true`. For example: | ||
Some service clients, such as {{% alias service=S3 %}}, may modify the endpoint | ||
returned by the resolver for certain service operations. For example, the {{% |
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.
nit: remove the
in For example, the Amazon S3
In resolution v2, `EndpointResolverV2` is the definitive mechanism through | ||
which endpoint resolution occurs. The resolver's `ResolveEndpoint` method is | ||
invoked as part of the workflow for every request you make in the SDK. The | ||
`Endpoint` value returned by the resolver is used **as-is** when making the |
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.
i think what you mean here is the hostname value given in Endpoint
right? because the path may get altered after endpoint resolution but before request execution. for example, the in S3 GetObject
requests, the Key
value will be added to the path during serialization
* `EndpointResolverV2` | ||
* `BaseEndpoint` | ||
|
||
## V1: `EndpointResolver` |
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.
yes, i agree
For changes to files under the
/codegen/aws-models
folder, and manual edits to autogenerated code (e.g./service/s3/api.go
) please create an Issue instead of a PR for those type of changes.If the PR addresses an existing bug or feature, please reference it here.
To help speed up the process and reduce the time to merge please ensure that
Allow edits by maintainers
is checked before submitting your PR. This will allow the project maintainers to make minor adjustments or improvements to the submitted PR, allow us to reduce the roundtrip time for merging your request.