Skip to main content

Getting Started

Installation

pip install capo-codepipeline

Usage

from capo_codepipeline import AsyncCodePipelineClient


async def main():
    async with AsyncCodePipelineClient() as code_pipeline:
        # Example: call the acknowledge_job operation
        response = await code_pipeline.acknowledge_job()
        print(response["status"])

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_codepipeline import AsyncCodePipelineClient


async def main():
    async with AsyncCodePipelineClient() as code_pipeline:
        # Example: paginate over list_action_executions
        async for item in code_pipeline.iter_list_action_executions():
            print(item)

Error Handling

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

from capo_codepipeline import AsyncCodePipelineClient
from capo_codepipeline.error import InvalidNonceException


async def main():
    async with AsyncCodePipelineClient() as code_pipeline:
        try:
            await code_pipeline.acknowledge_job()
        except InvalidNonceException 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_codepipeline import AsyncCodePipelineClient


async def main():
    async with AsyncCodePipelineClient() as code_pipeline:
        # Default: 3 attempts for every operation
        response = await code_pipeline.acknowledge_job()

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

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

Metadata

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

Built distribution (wheel)

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

Total release size: 643.9 kB

Release files / capo_codepipeline-0.6.0.tar.gz

Download URL capo_codepipeline-0.6.0.tar.gz
Size 181.1 kB
Tags Source
SHA-256 checksum
How to use checksums
47714b3e8c32dea9e6de1b62e5e837d8475b5369548b3eb9373140d3724eaf57
BLAKE2b-256 checksum
How to use checksums
6717f9d23281d0389f34a6ba2818cac952c7dd1e2d399d57ed5d946b0947f5ab
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_codepipeline-0.6.0-py3-none-any.whl

Download URL capo_codepipeline-0.6.0-py3-none-any.whl
Size 462.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b1766f1b692cb032b9dd166df6e0f10dc75b8a8c0aa86a29aad095ae55410cd3
BLAKE2b-256 checksum
How to use checksums
41843ad7a78b72732037174ad85d2fe5eb72af5b120d2a64712172fb5192c44f
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-codepipeline 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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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