how to configure retries in code with default configuration

i’d like to configure a client to use an non legacy retry mode, the docs reference doing that via code, but then we don’t get any of the default configuration behavior. ie. if we’re in ec2/ecs container the default would be to load region from the metadata endpoint, but passing an explicit config negates that lookup. applications shouldn’t have to reimplement the metadata server lookups just to get retry configuration options.

ie. on a server in us-east-2

>>> import boto3
>>> client = boto3.client('ec2')
>>> client._endpoint
ec2(https://ec2.us-east-2.amazonaws.com)

# per boto sdk docs on configuring retry
>>> config = Config(retries={'mode': 'adaptive', 'max_attempts': 10})
>>> boto3.client('ec2', config=Config)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/ubuntu/lib/python3.8/site-packages/boto3/__init__.py", line 93, in client
    return _get_default_session().client(*args, **kwargs)
  File "/home/ubuntu/lib/python3.8/site-packages/boto3/session.py", line 258, in client
    return self._session.create_client(
  File "/home/ubuntu/lib/python3.8/site-packages/botocore/session.py", line 797, in create_client
    region_name = self._resolve_region_name(region_name, config)
  File "/home/ubuntu/lib/python3.8/site-packages/botocore/session.py", line 848, in _resolve_region_name
    if config and config.region_name is not None:
AttributeError: type object 'Config' has no attribute 'region_name'

[kapilt]

@tjohanssonn your right this was user error, it does behave as expected wrt to config merge, sorry about the noise. i did end up using the RETRY env variables just to keep things consistent.

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.