Change timeout settings to merge them when configuration is merged (#3405)
## Motivation and Context <!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here --> For context, see https://github.com/smithy-lang/smithy-rs/discussions/3408 ## Description <!--- Describe your changes in detail --> - During `invoke`, load all timeout configs and merge them via a custom loader. - Fix config bag bugs that prevented using a Stored type that differed from `T`. - Add new e2e and codegen integration test validating that timeout settings are properly merged. - Add fallback for an empty timeout config being equivalent to `TimeoutConfig::disabled`. ## Checklist <!--- If a checkbox below is not applicable, then please DELETE it rather than leaving it unchecked --> - [x] I have updated `CHANGELOG.next.toml` if I made changes to the smithy-rs codegen or runtime crates - [x] I have updated `CHANGELOG.next.toml` if I made changes to the AWS SDK, generated SDK code, or SDK runtime crates ---- _By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice._ --------- Co-authored-by:John DiSanti <jdisanti@amazon.com>
Loading
Please register or sign in to comment