Getting Started
Installation
pip install capo-bedrock-data-automation-runtime
Usage
from capo_bedrock_data_automation_runtime import AsyncBedrockDataAutomationRuntimeClient
async def main():
async with AsyncBedrockDataAutomationRuntimeClient() as bedrock_data_automation_runtime:
# Example: call the invoke_data_automation operation
response = await bedrock_data_automation_runtime.invoke_data_automation()
print(response["output_configuration"])
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_bedrock_data_automation_runtime import AsyncBedrockDataAutomationRuntimeClient
from capo_bedrock_data_automation_runtime.error import AccessDeniedException
async def main():
async with AsyncBedrockDataAutomationRuntimeClient() as bedrock_data_automation_runtime:
try:
await bedrock_data_automation_runtime.invoke_data_automation()
except AccessDeniedException as e:
print(f"Error: {e}")
print(e.data) # additional error data
Retrying
The SDK retries failed operations automatically. Retry behaviour follows the Smithy specification: errors are retried based on their is_retryable and is_throttling_error attributes. Throttling errors use a longer base delay. Network-level failures (connection errors and timeouts) are also retried. Non-retryable errors, such as client errors without the @retryable trait, are raised immediately without further attempts.
The number of attempts defaults to 3 and can be changed at the client level via retry_max_attempts, or per call via config_overrides.
from capo_bedrock_data_automation_runtime import AsyncBedrockDataAutomationRuntimeClient
async def main():
async with AsyncBedrockDataAutomationRuntimeClient() as bedrock_data_automation_runtime:
# Default: 3 attempts for every operation
response = await bedrock_data_automation_runtime.invoke_data_automation()
# Override per operation
response = await bedrock_data_automation_runtime.invoke_data_automation(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await bedrock_data_automation_runtime.invoke_data_automation(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-bedrock-data-automation-runtime 0.9.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| capo_bedrock_data_automation_runtime-0.9.0.tar.gz | 69.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_bedrock_data_automation_runtime-0.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 178.7 kB
Release files / capo_bedrock_data_automation_runtime-0.9.0.tar.gz
| Download URL | capo_bedrock_data_automation_runtime-0.9.0.tar.gz |
|---|---|
| Size | 69.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
01359c09a42b91c0840d8cb0ade1f1d450235885c014936ca2eff2dc67bf8025
|
|
BLAKE2b-256 checksum How to use checksums |
39908c277c544354c738b0597c94bfc7fde296373d6a336dd3b836bdbb2f6588
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / capo_bedrock_data_automation_runtime-0.9.0-py3-none-any.whl
| Download URL | capo_bedrock_data_automation_runtime-0.9.0-py3-none-any.whl |
|---|---|
| Size | 109.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1ccecdc93ba2d3a0f923c6e39c85e849eaf1cfd2eee8c17b5c4d017e0d09034d
|
|
BLAKE2b-256 checksum How to use checksums |
4796c60f6901b2ebad8610ae369fc9389e9d88465c7ef6758a297c6046603dfc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for capo-bedrock-data-automation-runtime 0.9.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.