Skip to main content

Getting Started

Installation

pip install capo-resiliencehubv2

Usage

from capo_resiliencehubv2 import Asyncresiliencehubv2Client


async def main():
    async with Asyncresiliencehubv2Client() as resiliencehubv2:
        # Example: call the create_assertion operation
        response = await resiliencehubv2.create_assertion()
        print(response["assertion"])

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_resiliencehubv2 import Asyncresiliencehubv2Client


async def main():
    async with Asyncresiliencehubv2Client() as resiliencehubv2:
        # Example: paginate over list_assertions
        async for item in resiliencehubv2.iter_list_assertions():
            print(item)

Error Handling

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

from capo_resiliencehubv2 import Asyncresiliencehubv2Client
from capo_resiliencehubv2.error import AccessDeniedException


async def main():
    async with Asyncresiliencehubv2Client() as resiliencehubv2:
        try:
            await resiliencehubv2.create_assertion()
        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_resiliencehubv2 import Asyncresiliencehubv2Client


async def main():
    async with Asyncresiliencehubv2Client() as resiliencehubv2:
        # Default: 3 attempts for every operation
        response = await resiliencehubv2.create_assertion()

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

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

Metadata

Release files for capo-resiliencehubv2 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-resiliencehubv2 0.7.0
File Size Uploaded Provenance
capo_resiliencehubv2-0.7.0.tar.gz 192.7 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-resiliencehubv2 0.7.0
File Interpreter ABI Platform
capo_resiliencehubv2-0.7.0-py3-none-any.whl Python 3 none any Details

Total release size: 732.2 kB

Release files / capo_resiliencehubv2-0.7.0.tar.gz

Download URL capo_resiliencehubv2-0.7.0.tar.gz
Size 192.7 kB
Tags Source
SHA-256 checksum
How to use checksums
172b062e1a27d086f29a5ca184e683ea0cfc6db0374fcb7aaf7013e88075cd92
BLAKE2b-256 checksum
How to use checksums
6c056a36212c81385c156a49388a08b624b04b1b20271cbd47e288ef0c9513a7
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_resiliencehubv2-0.7.0-py3-none-any.whl

Download URL capo_resiliencehubv2-0.7.0-py3-none-any.whl
Size 539.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6bb7fc1ccb10cf50eb07537fe9f8d09509c8530cd416ca41dc939dbfea7146e8
BLAKE2b-256 checksum
How to use checksums
af25f1a8983dcd30a737e8450774e98477ba2edf40df39a656bff0a32b08337c
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-resiliencehubv2 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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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