Skip to main content

Getting Started

Installation

pip install capo-cloudhsm

Usage

from capo_cloudhsm import AsyncCloudHSMClient


async def main():
    async with AsyncCloudHSMClient() as cloud_hsm:
        # Example: call the add_tags_to_resource operation
        response = await cloud_hsm.add_tags_to_resource()
        print(response["status"])

Error Handling

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

from capo_cloudhsm import AsyncCloudHSMClient
from capo_cloudhsm.error import CloudHsmInternalException


async def main():
    async with AsyncCloudHSMClient() as cloud_hsm:
        try:
            await cloud_hsm.add_tags_to_resource()
        except CloudHsmInternalException 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_cloudhsm import AsyncCloudHSMClient


async def main():
    async with AsyncCloudHSMClient() as cloud_hsm:
        # Default: 3 attempts for every operation
        response = await cloud_hsm.add_tags_to_resource()

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

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

Metadata

Release files for capo-cloudhsm 0.6.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-cloudhsm 0.6.0
File Size Uploaded Provenance
capo_cloudhsm-0.6.0.tar.gz 79.9 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-cloudhsm 0.6.0
File Interpreter ABI Platform
capo_cloudhsm-0.6.0-py3-none-any.whl Python 3 none any Details

Total release size: 225.7 kB

Release files / capo_cloudhsm-0.6.0.tar.gz

Download URL capo_cloudhsm-0.6.0.tar.gz
Size 79.9 kB
Tags Source
SHA-256 checksum
How to use checksums
a20945323cfbf1bd4d8248b1d4002b734319eb1202b19fd2395c8b7ebb87fc97
BLAKE2b-256 checksum
How to use checksums
9f45e54e3ec9fb8b85fd434a9314ad41ff275d6b01df9dbd9f1cac9ba7b9dc22
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_cloudhsm-0.6.0-py3-none-any.whl

Download URL capo_cloudhsm-0.6.0-py3-none-any.whl
Size 145.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a31f4ec7ad2ec30e3e58c7edf05b0d6438e609b8be3f902a640dc1c501fcf83a
BLAKE2b-256 checksum
How to use checksums
d14595ed3166a7cb67321a780f3a6327910ee4195057341c4a3f5eac58ce3e0c
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-cloudhsm 0.6.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