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.3.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.3.0
File Size Uploaded Provenance
capo_cloudhsm-0.3.0.tar.gz 76.9 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 219.6 kB

Release files / capo_cloudhsm-0.3.0.tar.gz

Download URL capo_cloudhsm-0.3.0.tar.gz
Size 76.9 kB
Tags Source
SHA-256 checksum
How to use checksums
d0d3e057c0f79598fd36eaefb1b5a3dc991fb50afe3150226c4007a920f977f3
BLAKE2b-256 checksum
How to use checksums
bb2eed28e22827c13ecd75a7506064d38a49cf361b8167092783e56437da45a8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","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.3.0-py3-none-any.whl

Download URL capo_cloudhsm-0.3.0-py3-none-any.whl
Size 142.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4eba332a4558c009d6a14d0e2144226315f762a005eaa5498a52fa05395faaf9
BLAKE2b-256 checksum
How to use checksums
643969a141a7a82f4361ff26f94a9337ebb3abd548e04df59ff2ed1fe8fdf73f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","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.3.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