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.5.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.5.0
File Size Uploaded Provenance
capo_resiliencehubv2-0.5.0.tar.gz 186.7 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 719.1 kB

Release files / capo_resiliencehubv2-0.5.0.tar.gz

Download URL capo_resiliencehubv2-0.5.0.tar.gz
Size 186.7 kB
Tags Source
SHA-256 checksum
How to use checksums
ee7dbe275be839da554aabfc221d0fbf97e57d721415de74dac841f1ec544b48
BLAKE2b-256 checksum
How to use checksums
9750d9c1f4f61f909001b63a1d3aff72d46d9d61811ec5595e4e864d90ea6765
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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.5.0-py3-none-any.whl

Download URL capo_resiliencehubv2-0.5.0-py3-none-any.whl
Size 532.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
349a3629b23ae5e8d3b17d1da0a2c18df31f40a36e3a48b5d64c8d01fda422cc
BLAKE2b-256 checksum
How to use checksums
e3d8d7106e1c306ed7a23edc8a8199d08f1653df54c9980a751c129b54af58c2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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.5.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