Skip to main content

Getting Started

Installation

pip install capo-apprunner

Usage

from capo_apprunner import AsyncAppRunnerClient


async def main():
    async with AsyncAppRunnerClient() as app_runner:
        # Example: call the associate_custom_domain operation
        response = await app_runner.associate_custom_domain()
        print(response["dns_target"])

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_apprunner import AsyncAppRunnerClient


async def main():
    async with AsyncAppRunnerClient() as app_runner:
        # Example: paginate over describe_custom_domains
        async for item in app_runner.iter_describe_custom_domains():
            print(item)

Error Handling

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

from capo_apprunner import AsyncAppRunnerClient
from capo_apprunner.error import InternalServiceErrorException


async def main():
    async with AsyncAppRunnerClient() as app_runner:
        try:
            await app_runner.associate_custom_domain()
        except InternalServiceErrorException 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_apprunner import AsyncAppRunnerClient


async def main():
    async with AsyncAppRunnerClient() as app_runner:
        # Default: 3 attempts for every operation
        response = await app_runner.associate_custom_domain()

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

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

Metadata

Release files for capo-apprunner 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-apprunner 0.6.0
File Size Uploaded Provenance
capo_apprunner-0.6.0.tar.gz 124.1 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 407.6 kB

Release files / capo_apprunner-0.6.0.tar.gz

Download URL capo_apprunner-0.6.0.tar.gz
Size 124.1 kB
Tags Source
SHA-256 checksum
How to use checksums
3d46921129d8574c9526d282ab1545e89a0d617c145922c64d4bf270ebbde19f
BLAKE2b-256 checksum
How to use checksums
85a1f9f31ec8a416c40b9abaded6f376d8cdc8895d2fc1205a3e309eab5590e6
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_apprunner-0.6.0-py3-none-any.whl

Download URL capo_apprunner-0.6.0-py3-none-any.whl
Size 283.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1c126052a8840c3fe0169e0385765bf8dcc7d2c440e579dbec7fd4359e6fd761
BLAKE2b-256 checksum
How to use checksums
87f23311e5b0dc2b1cb0b0c97d9af0749794a38b9459c2ffd05dc5dd90c0b806
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-apprunner 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