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.4.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.4.0
File Size Uploaded Provenance
capo_cloudhsm-0.4.0.tar.gz 77.2 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 220.4 kB

Release files / capo_cloudhsm-0.4.0.tar.gz

Download URL capo_cloudhsm-0.4.0.tar.gz
Size 77.2 kB
Tags Source
SHA-256 checksum
How to use checksums
5be4c30ee59a3dc9485134de27f8fbe00046486fafc7154c5ced289c091f42f5
BLAKE2b-256 checksum
How to use checksums
6a98228e5f1e5534d7278eb67c64173923c7632723e4287c287c3395a380c759
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_cloudhsm-0.4.0-py3-none-any.whl

Download URL capo_cloudhsm-0.4.0-py3-none-any.whl
Size 143.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9e2a5d62f56c636744facd27ad781d77630a17e3e1796ab4b2eb686f6a0385b7
BLAKE2b-256 checksum
How to use checksums
7d6bcb97261eb6cbcf978096e54aa5c190bc643be3c4b87d97a30500581a466e
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-cloudhsm 0.4.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