Skip to main content

Getting Started

Installation

pip install capo-backup

Usage

from capo_backup import AsyncBackupClient


async def main():
    async with AsyncBackupClient() as backup:
        # Example: call the associate_backup_vault_mpa_approval_team operation
        response = await backup.associate_backup_vault_mpa_approval_team()
        print(response)

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_backup import AsyncBackupClient


async def main():
    async with AsyncBackupClient() as backup:
        # Example: paginate over list_backup_jobs
        async for item in backup.iter_list_backup_jobs():
            print(item)

Error Handling

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

from capo_backup import AsyncBackupClient
from capo_backup.error import InvalidParameterValueException


async def main():
    async with AsyncBackupClient() as backup:
        try:
            await backup.associate_backup_vault_mpa_approval_team()
        except InvalidParameterValueException 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_backup import AsyncBackupClient


async def main():
    async with AsyncBackupClient() as backup:
        # Default: 3 attempts for every operation
        response = await backup.associate_backup_vault_mpa_approval_team()

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

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

Metadata

Release files for capo-backup 0.2.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-backup 0.2.0
File Size Uploaded Provenance
capo_backup-0.2.0.tar.gz 282.5 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-backup 0.2.0
File Interpreter ABI Platform
capo_backup-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 983.2 kB

Release files / capo_backup-0.2.0.tar.gz

Download URL capo_backup-0.2.0.tar.gz
Size 282.5 kB
Tags Source
SHA-256 checksum
How to use checksums
d6cbadea97df2ac86df3a356cd1677a8d622354a08d137dd1b72a2f10b120aa6
BLAKE2b-256 checksum
How to use checksums
6c2680a85b522bb4fb2ffaca398fff9598fa986ac6e5b84ba508982f08d72326
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","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_backup-0.2.0-py3-none-any.whl

Download URL capo_backup-0.2.0-py3-none-any.whl
Size 700.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a74ef55b6d51251abe30d4c8b0c2729e9d92e90e71328f414810f817d2097536
BLAKE2b-256 checksum
How to use checksums
73598caeea9f169e78b722021aa08b7a31c9425b8a8613eede5fc06a46ab6130
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","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-backup 0.2.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