Breaking changes in 0.10.0: async client configuration
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- aws, python
- Domain
- documentation
Research direction
No repository file or test is named. Start by checking where release notes or migration documentation for version 0.10.0 are maintained, then compare the documented AsyncConfig imports, resolve() usage, plugin types, and version-pinning examples with the issue; done means the breaking-change guidance is published in the project’s established documentation location.
Written by the indexing model from the issue text.
Description
Breaking changes in 0.10.0 release
Starting with version 0.10.0, the aws-sdk-* client packages include breaking changes to client configuration.
New configuration object
The synchronous Config class previously exported from each service package has been replaced with a service-specific asynchronous configuration class.
For example, for Bedrock Runtime:
# Before
from aws_sdk_bedrock_runtime.config import Config
is now:
# 0.10.0 and later
from aws_sdk_bedrock_runtime.config import AsyncBedrockRuntimeConfig
Configuration is now asynchronous
Configuration objects must now be created using the asynchronous resolve() method. Directly instantiating the configuration class is not supported and results in an error.
# Incorrect
config = AsyncBedrockRuntimeConfig(
region="us-west-2",
)
# Raises
smithy_aws_core.config.exceptions.ConfigError: AsyncBedrockRuntimeConfig cannot be constructed directly. Use `await AsyncBedrockRuntimeConfig.resolve(...)` instead.
Instead, resolve the configuration before passing it to the client:
from aws_sdk_bedrock_runtime.config import AsyncBedrockRuntimeConfig
config = await AsyncBedrockRuntimeConfig.resolve(
region="us-west-2",
)
This change allows the SDK to perform configuration resolution that requires I/O, such as reading shared AWS configuration and credentials files, without blocking the event loop.
Configuration values are resolved from explicit overrides passed to resolve(), environment variables, and shared AWS configuration and credentials files. If no configuration is provided when constructing a client, the SDK automatically resolves one for you.
Plugins
Configuration plugins must now receive the service-specific asynchronous configuration type, Async<ServiceId>Config, instead of the previous Config type.
For example:
# Before
from aws_sdk_bedrock_runtime.config import Config
def my_plugin(config: Config) -> None:
...
is now:
# 0.10.0 and later
from aws_sdk_bedrock_runtime.config import AsyncBedrockRuntimeConfig
def my_plugin(config: AsyncBedrockRuntimeConfig) -> None:
...
Migrating existing applications
Update configuration usage as follows:
- Replace imports of
Configwith the service-specificAsync<ServiceId>Config. - Replace direct configuration construction with
await Async<ServiceId>Config.resolve(...). - Ensure explicit configuration resolution occurs within an asynchronous context.
- Update configuration plugins to accept the service-specific
Async<ServiceId>Configtype instead ofConfig.
For example:
# Before
from aws_sdk_bedrock_runtime.client import AsyncBedrockRuntimeClient
from aws_sdk_bedrock_runtime.config import Config
def my_plugin(config: Config) -> None:
...
config = Config(
region="us-west-2",
)
client = AsyncBedrockRuntimeClient(
config=config,
plugins=[my_plugin],
)
becomes:
# 0.10.0 and later
from aws_sdk_bedrock_runtime.client import AsyncBedrockRuntimeClient
from aws_sdk_bedrock_runtime.config import AsyncBedrockRuntimeConfig
def my_plugin(config: AsyncBedrockRuntimeConfig) -> None:
...
config = await AsyncBedrockRuntimeConfig.resolve(
region="us-west-2",
)
client = AsyncBedrockRuntimeClient(
config=config,
plugins=[my_plugin],
)
Installing the latest version
Upgrade an existing client package with pip:
python -m pip install --upgrade aws-sdk-<service-id>
For example:
python -m pip install --upgrade aws-sdk-bedrock-runtime
To explicitly require version 0.10.0 or later:
python -m pip install "aws-sdk-bedrock-runtime>=0.10.0"
Pinning versions
To avoid unexpected breaking changes when installing or deploying your application, we recommend pinning aws-sdk-* client packages to a specific version or compatible version range.
To pin to an exact version:
python -m pip install "aws-sdk-bedrock-runtime==0.10.0"
To allow compatible patch releases while avoiding newer minor releases:
python -m pip install "aws-sdk-bedrock-runtime~=0.10.0"
This is important while the SDK is pre-1.0.0, when minor releases may include breaking changes.
- Dominant language
- Python
- Stars
- 171
- Forks
- 24
- Avg merge
- 10h 47m
- Merged PRs (30d)
- 7
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws/aws-sdk-python
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aws/aws-sdk-python#13 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
aws/aws-sdk-python#99 ·
-
Support Python 3.11 Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
aws/aws-sdk-python#92 ·
-
announcement
Difficulty 5/5 Over a week Newbie friendliness 25/100
aws/aws-sdk-python#90 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
aws/aws-sdk-python#18 ·
All issues in aws/aws-sdk-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100