Route auto resolve to classic for unsupported workloads - #10631
Merged
Conversation
ashovlin
approved these changes
Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements control flow for cases where
preferred_transfer_client = auto:AWS_CLI_AUTO_RESOLVE_CLIENT. If it's NOTcrt, then resolve to Python. This means that unless this env var check passes, the following steps will never even fire.a.
max_bandwidthis explicitly configured.b. Resolved retry mode is
adaptive.c. Transfer operation is an upload from a non-seekable stream.
Note that today, this is a no-op unless
AWS_CLI_AUTO_RESOLVE_CLIENT = 'crt'.