Skip to main content

Getting Started

Installation

pip install capo-resiliencehub

Usage

from capo_resiliencehub import AsyncresiliencehubClient


async def main():
    async with AsyncresiliencehubClient() as resiliencehub:
        # Example: call the accept_resource_grouping_recommendations operation
        response = await resiliencehub.accept_resource_grouping_recommendations()
        print(response["app_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_resiliencehub import AsyncresiliencehubClient


async def main():
    async with AsyncresiliencehubClient() as resiliencehub:
        # Example: paginate over list_alarm_recommendations
        async for item in resiliencehub.iter_list_alarm_recommendations():
            print(item)

Error Handling

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

from capo_resiliencehub import AsyncresiliencehubClient
from capo_resiliencehub.error import AccessDeniedException


async def main():
    async with AsyncresiliencehubClient() as resiliencehub:
        try:
            await resiliencehub.accept_resource_grouping_recommendations()
        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_resiliencehub import AsyncresiliencehubClient


async def main():
    async with AsyncresiliencehubClient() as resiliencehub:
        # Default: 3 attempts for every operation
        response = await resiliencehub.accept_resource_grouping_recommendations()

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

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

Metadata

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

Built distribution (wheel)

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

Total release size: 678.4 kB

Release files / capo_resiliencehub-0.7.0.tar.gz

Download URL capo_resiliencehub-0.7.0.tar.gz
Size 189.1 kB
Tags Source
SHA-256 checksum
How to use checksums
6ad7952ebff9f333cd9762e2b07882177ce5ebf9ceff47fa2caf8e596f5e4ff9
BLAKE2b-256 checksum
How to use checksums
5e1f3763e5b41b2e0a8eb2c45177ebd49a47b68e446a23985cdf2e329585863d
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_resiliencehub-0.7.0-py3-none-any.whl

Download URL capo_resiliencehub-0.7.0-py3-none-any.whl
Size 489.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f5c668ccd902d6cf6a96e35115ff377915ec34ef50f8818f1a6a382cae185873
BLAKE2b-256 checksum
How to use checksums
e63656058299c0f62fb496ee75ee2909c92eaa7a4e28acb34e4130acd0484790
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-resiliencehub 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