Skip to main content

Getting Started

Installation

pip install capo-cloudfront-keyvaluestore

Usage

from capo_cloudfront_keyvaluestore import AsyncCloudFrontKeyValueStoreClient


async def main():
    async with AsyncCloudFrontKeyValueStoreClient() as cloud_front_key_value_store:
        # Example: call the delete_key operation
        response = await cloud_front_key_value_store.delete_key()
        print(response["item_count"])

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_cloudfront_keyvaluestore import AsyncCloudFrontKeyValueStoreClient


async def main():
    async with AsyncCloudFrontKeyValueStoreClient() as cloud_front_key_value_store:
        # Example: paginate over list_keys
        async for item in cloud_front_key_value_store.iter_list_keys():
            print(item)

Error Handling

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

from capo_cloudfront_keyvaluestore import AsyncCloudFrontKeyValueStoreClient
from capo_cloudfront_keyvaluestore.error import AccessDeniedException


async def main():
    async with AsyncCloudFrontKeyValueStoreClient() as cloud_front_key_value_store:
        try:
            await cloud_front_key_value_store.delete_key()
        except AccessDeniedException 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_cloudfront_keyvaluestore import AsyncCloudFrontKeyValueStoreClient


async def main():
    async with AsyncCloudFrontKeyValueStoreClient() as cloud_front_key_value_store:
        # Default: 3 attempts for every operation
        response = await cloud_front_key_value_store.delete_key()

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

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

Metadata

Release files for capo-cloudfront-keyvaluestore 0.5.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-cloudfront-keyvaluestore 0.5.0
File Size Uploaded Provenance
capo_cloudfront_keyvaluestore-0.5.0.tar.gz 59.8 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-cloudfront-keyvaluestore 0.5.0
File Interpreter ABI Platform
capo_cloudfront_keyvaluestore-0.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 146.6 kB

Release files / capo_cloudfront_keyvaluestore-0.5.0.tar.gz

Download URL capo_cloudfront_keyvaluestore-0.5.0.tar.gz
Size 59.8 kB
Tags Source
SHA-256 checksum
How to use checksums
920daef306bb379f3459482b7e76d24394c8696310ae39f9596962fb0c711a90
BLAKE2b-256 checksum
How to use checksums
0b97614e59fba6bfe50c376753d538170a285e568f8209301bb835153834c645
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_cloudfront_keyvaluestore-0.5.0-py3-none-any.whl

Download URL capo_cloudfront_keyvaluestore-0.5.0-py3-none-any.whl
Size 86.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
afba966d7ccb7021e30e9a5a17a91d69b67cbc80f07cd6a42c2318a06d8acb50
BLAKE2b-256 checksum
How to use checksums
9b34c012b72ba19b844824ddd0628e5aff4e9dc73857a8d66b91ebeb9cb2eced
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-cloudfront-keyvaluestore 0.5.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