Skip to main content

Getting Started

Installation

pip install capo-accessanalyzer

Usage

from capo_accessanalyzer import AsyncAccessAnalyzerClient


async def main():
    async with AsyncAccessAnalyzerClient() as access_analyzer:
        # Example: call the apply_archive_rule operation
        response = await access_analyzer.apply_archive_rule()
        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_accessanalyzer import AsyncAccessAnalyzerClient


async def main():
    async with AsyncAccessAnalyzerClient() as access_analyzer:
        # Example: paginate over get_finding_recommendation
        async for item in access_analyzer.iter_get_finding_recommendation():
            print(item)

Error Handling

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

from capo_accessanalyzer import AsyncAccessAnalyzerClient
from capo_accessanalyzer.error import AccessDeniedException


async def main():
    async with AsyncAccessAnalyzerClient() as access_analyzer:
        try:
            await access_analyzer.apply_archive_rule()
        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_accessanalyzer import AsyncAccessAnalyzerClient


async def main():
    async with AsyncAccessAnalyzerClient() as access_analyzer:
        # Default: 3 attempts for every operation
        response = await access_analyzer.apply_archive_rule()

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

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

Metadata

Release files for capo-accessanalyzer 0.7.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-accessanalyzer 0.7.0
File Size Uploaded Provenance
capo_accessanalyzer-0.7.0.tar.gz 146.0 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-accessanalyzer 0.7.0
File Interpreter ABI Platform
capo_accessanalyzer-0.7.0-py3-none-any.whl Python 3 none any Details

Total release size: 503.4 kB

Release files / capo_accessanalyzer-0.7.0.tar.gz

Download URL capo_accessanalyzer-0.7.0.tar.gz
Size 146.0 kB
Tags Source
SHA-256 checksum
How to use checksums
403380aa3d88cc4b4471225c0f2d0e1e2c7a426d60654c8c411cd93b62c7c284
BLAKE2b-256 checksum
How to use checksums
297e4abfd0e14bd17571569e2d70d81c31b42f48238efb8688e3f39875fd1b04
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_accessanalyzer-0.7.0-py3-none-any.whl

Download URL capo_accessanalyzer-0.7.0-py3-none-any.whl
Size 357.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e3dff9fd6b611ed0603fe79ee45d6ee3df21104b51fc00403b44a3d76769a89f
BLAKE2b-256 checksum
How to use checksums
96a396833a55f360a3a731ac2e1bb51c408a7fd925b814222651b67a7f6c06bc
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-accessanalyzer 0.7.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