Skip to main content

Getting Started

Installation

pip install capo-bcm-dashboards

Usage

from capo_bcm_dashboards import AsyncBCMDashboardsClient


async def main():
    async with AsyncBCMDashboardsClient() as bcm_dashboards:
        # Example: call the create_dashboard operation
        response = await bcm_dashboards.create_dashboard()
        print(response["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_bcm_dashboards import AsyncBCMDashboardsClient


async def main():
    async with AsyncBCMDashboardsClient() as bcm_dashboards:
        # Example: paginate over list_dashboards
        async for item in bcm_dashboards.iter_list_dashboards():
            print(item)

Error Handling

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

from capo_bcm_dashboards import AsyncBCMDashboardsClient
from capo_bcm_dashboards.error import AccessDeniedException


async def main():
    async with AsyncBCMDashboardsClient() as bcm_dashboards:
        try:
            await bcm_dashboards.create_dashboard()
        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_bcm_dashboards import AsyncBCMDashboardsClient


async def main():
    async with AsyncBCMDashboardsClient() as bcm_dashboards:
        # Default: 3 attempts for every operation
        response = await bcm_dashboards.create_dashboard()

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

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

Metadata

Release files for capo-bcm-dashboards 0.4.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-bcm-dashboards 0.4.0
File Size Uploaded Provenance
capo_bcm_dashboards-0.4.0.tar.gz 86.0 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-bcm-dashboards 0.4.0
File Interpreter ABI Platform
capo_bcm_dashboards-0.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 248.8 kB

Release files / capo_bcm_dashboards-0.4.0.tar.gz

Download URL capo_bcm_dashboards-0.4.0.tar.gz
Size 86.0 kB
Tags Source
SHA-256 checksum
How to use checksums
c05db2c599342acf5f4fd651913926bdabaf30cb85e3152a1a32ac51b8344ad7
BLAKE2b-256 checksum
How to use checksums
2e1553560952e7233d67a8424d5d0a188718815ef3db00519221aaf71e51d379
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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_bcm_dashboards-0.4.0-py3-none-any.whl

Download URL capo_bcm_dashboards-0.4.0-py3-none-any.whl
Size 162.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e7ee01c149c239c246cc875ce7f5231b0ceb725729882aa5a70aeeadf41dc5f8
BLAKE2b-256 checksum
How to use checksums
215d273dd5fb8238192fa5ed426af057601ba0daa173c0877c80803163bdbc64
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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-bcm-dashboards 0.4.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