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

Endpoints 2.0 #1784

Closed
8 of 14 tasks
jdisanti opened this issue Sep 29, 2022 · 0 comments · Fixed by #1953
Closed
8 of 14 tasks

Endpoints 2.0 #1784

jdisanti opened this issue Sep 29, 2022 · 0 comments · Fixed by #1953
Assignees
Labels
client sdk sdk-ga tracking Meta-issues to track overall progress

Comments

@jdisanti
Copy link
Collaborator

jdisanti commented Sep 29, 2022

The approach for endpoint resolution is being redone to better support the edge cases without customizations. This is the tracking issue for that work.

implementation work

testing:

  • presigned URL canary
  • canary with force path style
  • canary with virtual addressing
  • s3 object lambda tests

native smithy

  • documentation of how native smithy services can codegenerate an endpoint resolver
  • add a default middleware for native smithy services that sets the endpoint on the request
@jdisanti jdisanti added tracking Meta-issues to track overall progress client sdk labels Sep 29, 2022
@jdisanti jdisanti moved this to In Progress in AWS Rust SDK Public Roadmap Sep 29, 2022
@Velfi Velfi assigned rcoh and unassigned Velfi Oct 27, 2022
@rcoh rcoh linked a pull request Nov 14, 2022 that will close this issue
Repository owner moved this from In Progress to Done in AWS Rust SDK Public Roadmap Nov 16, 2022
@rcoh rcoh reopened this Nov 28, 2022
@rcoh rcoh mentioned this issue Dec 21, 2022
@goabv goabv added the sdk-ga label Feb 6, 2023
@rcoh rcoh closed this as completed Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client sdk sdk-ga tracking Meta-issues to track overall progress
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants