Skip to main content

Getting Started

Installation

pip install capo-config-service

Usage

from capo_config_service import AsyncConfigServiceClient


async def main():
    async with AsyncConfigServiceClient() as config_service:
        # Example: call the associate_resource_types operation
        response = await config_service.associate_resource_types()
        print(response["configuration_recorder"])

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_config_service import AsyncConfigServiceClient


async def main():
    async with AsyncConfigServiceClient() as config_service:
        # Example: paginate over describe_aggregate_compliance_by_config_rules
        async for item in config_service.iter_describe_aggregate_compliance_by_config_rules():
            print(item)

Error Handling

The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.

from capo_config_service import AsyncConfigServiceClient
from capo_config_service.error import ConflictException


async def main():
    async with AsyncConfigServiceClient() as config_service:
        try:
            await config_service.associate_resource_types()
        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_config_service import AsyncConfigServiceClient


async def main():
    async with AsyncConfigServiceClient() as config_service:
        # Default: 3 attempts for every operation
        response = await config_service.associate_resource_types()

        # Override per operation
        response = await config_service.associate_resource_types(config_overrides={"retry_max_attempts": 5})

        # Disable retries for this call
        response = await config_service.associate_resource_types(config_overrides={"retry_max_attempts": 1})

Metadata

Release files for capo-config-service 0.10.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for capo-config-service 0.10.0
File Size Uploaded Provenance
capo_config_service-0.10.0.tar.gz 317.5 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-config-service 0.10.0
File Interpreter ABI Platform
capo_config_service-0.10.0-py3-none-any.whl Python 3 none any Details

Total release size: 1.1 MB

Release files / capo_config_service-0.10.0.tar.gz

Download URL capo_config_service-0.10.0.tar.gz
Size 317.5 kB
Tags Source
SHA-256 checksum
How to use checksums
10aea3883b1424b4206a874858f47d48dc9a70ff9282ac77d48a3acaa6f770e5
BLAKE2b-256 checksum
How to use checksums
e9cad3983f91379d332b5b2664f0547f202da7c8bcbe3e090df2d88556359c42
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_config_service-0.10.0-py3-none-any.whl

Download URL capo_config_service-0.10.0-py3-none-any.whl
Size 831.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4b749596bdbe96e5e65fd4f11c072bacc5f9cf32e0b2f6fbaa0417a8d3943838
BLAKE2b-256 checksum
How to use checksums
88a1e5df72c6a2bdf5ca66fedd19232b36a8500eaa27576b604ecfd059f3498d
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-config-service 0.10.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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page