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

Complete client timeouts with sdk-default-configuration.json #1732

Open
3 of 6 tasks
jdisanti opened this issue Sep 13, 2022 · 0 comments
Open
3 of 6 tasks

Complete client timeouts with sdk-default-configuration.json #1732

jdisanti opened this issue Sep 13, 2022 · 0 comments
Labels
breaking-change This will require a breaking change sdk tracking Meta-issues to track overall progress
Milestone

Comments

@jdisanti
Copy link
Collaborator

jdisanti commented Sep 13, 2022

This issue tracks implementation of handling the sdk-default-configuration.json model file for client-side request timeouts.

  • Pull in the sdk-default-configuration.json file with the rest of the models during releases
  • Add API to select retry mode in SdkConfig and service Config (needs RFC)
  • Add ability to override timeout config for individual requests (needs RFC)
  • Implement retry mode value resolution logic that occurs at code generation time (multiple/add/override modes that apply to the base config values)
  • Implement "auto mode" for timeout value resolution
  • Verify if stsRegionalEndpoints and s3UsEast1RegionalEndpoints default configuration values are still relevant after endpoints 2.0, and implement if so
@jdisanti jdisanti added tracking Meta-issues to track overall progress breaking-change This will require a breaking change labels Sep 13, 2022
@jdisanti jdisanti mentioned this issue Sep 13, 2022
5 tasks
@Velfi Velfi added this to the SDK GA milestone Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change This will require a breaking change sdk tracking Meta-issues to track overall progress
Projects
None yet
Development

No branches or pull requests

2 participants