Skip to main content

Getting Started

Installation

pip install capo-route53-recovery-control-config

Usage

from capo_route53_recovery_control_config import AsyncRoute53RecoveryControlConfigClient


async def main():
    async with AsyncRoute53RecoveryControlConfigClient() as route53_recovery_control_config:
        # Example: call the create_cluster operation
        response = await route53_recovery_control_config.create_cluster()
        print(response["cluster"])

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_route53_recovery_control_config import AsyncRoute53RecoveryControlConfigClient


async def main():
    async with AsyncRoute53RecoveryControlConfigClient() as route53_recovery_control_config:
        # Example: paginate over list_associated_route53_health_checks
        async for item in route53_recovery_control_config.iter_list_associated_route53_health_checks():
            print(item)

Error Handling

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

from capo_route53_recovery_control_config import AsyncRoute53RecoveryControlConfigClient
from capo_route53_recovery_control_config.error import AccessDeniedException


async def main():
    async with AsyncRoute53RecoveryControlConfigClient() as route53_recovery_control_config:
        try:
            await route53_recovery_control_config.create_cluster()
        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_route53_recovery_control_config import AsyncRoute53RecoveryControlConfigClient


async def main():
    async with AsyncRoute53RecoveryControlConfigClient() as route53_recovery_control_config:
        # Default: 3 attempts for every operation
        response = await route53_recovery_control_config.create_cluster()

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

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

Metadata

Release files for capo-route53-recovery-control-config 0.7.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-route53-recovery-control-config 0.7.0
File Size Uploaded Provenance
capo_route53_recovery_control_config-0.7.0.tar.gz 88.9 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-route53-recovery-control-config 0.7.0
File Interpreter ABI Platform
capo_route53_recovery_control_config-0.7.0-py3-none-any.whl Python 3 none any Details

Total release size: 276.2 kB

Release files / capo_route53_recovery_control_config-0.7.0.tar.gz

Download URL capo_route53_recovery_control_config-0.7.0.tar.gz
Size 88.9 kB
Tags Source
SHA-256 checksum
How to use checksums
4a2848fc8036bf434d494492037ee0ac8fc72bff3c03e380b6c29d2e5a5568df
BLAKE2b-256 checksum
How to use checksums
8f5fb7ad142522753ed734a34e658e07d12c8c2e86ef3392081adcd37ce89a6d
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_route53_recovery_control_config-0.7.0-py3-none-any.whl

Download URL capo_route53_recovery_control_config-0.7.0-py3-none-any.whl
Size 187.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bc4039214490f44e00f9fda799dc6affe1882d313f2a4d3e84e50c9e65a359e7
BLAKE2b-256 checksum
How to use checksums
7238981c40f9a4a447c6173ca429dc17aab0d3ab19af4369e63001db144ca9c6
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-route53-recovery-control-config 0.7.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