Skip to main content

Getting Started

Installation

pip install capo-kinesis-analytics-v2

Usage

from capo_kinesis_analytics_v2 import AsyncKinesisAnalyticsV2Client


async def main():
    async with AsyncKinesisAnalyticsV2Client() as kinesis_analytics_v2:
        # Example: call the add_application_cloud_watch_logging_option operation
        response = await kinesis_analytics_v2.add_application_cloud_watch_logging_option()
        print(response["application_arn"])

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_kinesis_analytics_v2 import AsyncKinesisAnalyticsV2Client


async def main():
    async with AsyncKinesisAnalyticsV2Client() as kinesis_analytics_v2:
        # Example: paginate over list_application_operations
        async for item in kinesis_analytics_v2.iter_list_application_operations():
            print(item)

Error Handling

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

from capo_kinesis_analytics_v2 import AsyncKinesisAnalyticsV2Client
from capo_kinesis_analytics_v2.error import ConcurrentModificationException


async def main():
    async with AsyncKinesisAnalyticsV2Client() as kinesis_analytics_v2:
        try:
            await kinesis_analytics_v2.add_application_cloud_watch_logging_option()
        except ConcurrentModificationException 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_kinesis_analytics_v2 import AsyncKinesisAnalyticsV2Client


async def main():
    async with AsyncKinesisAnalyticsV2Client() as kinesis_analytics_v2:
        # Default: 3 attempts for every operation
        response = await kinesis_analytics_v2.add_application_cloud_watch_logging_option()

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

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

Metadata

Release files for capo-kinesis-analytics-v2 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-kinesis-analytics-v2 0.6.0
File Size Uploaded Provenance
capo_kinesis_analytics_v2-0.6.0.tar.gz 149.7 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-kinesis-analytics-v2 0.6.0
File Interpreter ABI Platform
capo_kinesis_analytics_v2-0.6.0-py3-none-any.whl Python 3 none any Details

Total release size: 536.9 kB

Release files / capo_kinesis_analytics_v2-0.6.0.tar.gz

Download URL capo_kinesis_analytics_v2-0.6.0.tar.gz
Size 149.7 kB
Tags Source
SHA-256 checksum
How to use checksums
846de8e1e187362dfc20e7586af043b088be1d0829c3a475b46c2ad2aec5f72a
BLAKE2b-256 checksum
How to use checksums
60eb6666f52a149fb432473b7868256b9d0829023cc14c02285f9d9eaa69ac9b
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_kinesis_analytics_v2-0.6.0-py3-none-any.whl

Download URL capo_kinesis_analytics_v2-0.6.0-py3-none-any.whl
Size 387.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fdfbff499f662c5709764b056948bea8e061f6e9bd29526449e8f075a00cafda
BLAKE2b-256 checksum
How to use checksums
a91a6fc338a006774d83bf0414596cb4d2b7bc53dbd633fe0507c22cf7ccaa00
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-kinesis-analytics-v2 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