capo-oam: typed, async Python SDK for AWS OAM
capo-oam is a typed Python SDK for AWS OAM. It has an async client, AsyncOAMClient, for asyncio and trio, and a sync client, OAMClient, with the same methods. Requests and responses are typed with TypedDicts, so your editor and type checker know every field.
It is part of capo, a community-driven alternative to boto3 and aioboto3, built on its own HTTP stack instead of botocore and generated from the official AWS Smithy models. Documentation: https://capo-sdk.dev/services/oam/
Installation
pip install capo-oam
Usage
from capo_oam import AsyncOAMClient
async def main():
async with AsyncOAMClient() as oam:
# Example: call the create_link operation
response = await oam.create_link()
print(response["arn"])
Pagination
Some operations in this SDK support pagination. If the operation supports pagination it will have an iter_ prefixed method that returns an async iterator.
from capo_oam import AsyncOAMClient
async def main():
async with AsyncOAMClient() as oam:
# Example: paginate over list_attached_links
async for item in oam.iter_list_attached_links():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_oam import AsyncOAMClient
from capo_oam.error import ConflictException
async def main():
async with AsyncOAMClient() as oam:
try:
await oam.create_link()
except ConflictException 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_oam import AsyncOAMClient
async def main():
async with AsyncOAMClient() as oam:
# Default: 3 attempts for every operation
response = await oam.create_link()
# Override per operation
response = await oam.create_link(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await oam.create_link(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-oam 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_oam-0.9.0.tar.gz | 81.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_oam-0.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 216.8 kB
Release files / capo_oam-0.9.0.tar.gz
| Download URL | capo_oam-0.9.0.tar.gz |
|---|---|
| Size | 81.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ad4be0cbe891da674b90d78e541d99affa9e14a311ab92920086c0e9c56663c
|
|
BLAKE2b-256 checksum How to use checksums |
a7d55d17399db8f499af4fc1f880326c4dd64ad41ce5398e88ffc3f1aa44493d
|
| 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_oam-0.9.0-py3-none-any.whl
| Download URL | capo_oam-0.9.0-py3-none-any.whl |
|---|---|
| Size | 135.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fcbc4c60a2623616fa191e10603530d935af6efbefc50b1bc2ee03b7d3741fd6
|
|
BLAKE2b-256 checksum How to use checksums |
e712fce953c972e69a25fadb5dd54bc235b9ed43df7fe433a42349e0507bd2a2
|
| 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-oam 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.