Skip to main content

Getting Started

Installation

pip install capo-service-catalog-appregistry

Usage

from capo_service_catalog_appregistry import AsyncServiceCatalogAppRegistryClient


async def main():
    async with AsyncServiceCatalogAppRegistryClient() as service_catalog_app_registry:
        # Example: call the associate_attribute_group operation
        response = await service_catalog_app_registry.associate_attribute_group()
        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_service_catalog_appregistry import AsyncServiceCatalogAppRegistryClient


async def main():
    async with AsyncServiceCatalogAppRegistryClient() as service_catalog_app_registry:
        # Example: paginate over list_applications
        async for item in service_catalog_app_registry.iter_list_applications():
            print(item)

Error Handling

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

from capo_service_catalog_appregistry import AsyncServiceCatalogAppRegistryClient
from capo_service_catalog_appregistry.error import ConflictException


async def main():
    async with AsyncServiceCatalogAppRegistryClient() as service_catalog_app_registry:
        try:
            await service_catalog_app_registry.associate_attribute_group()
        except ConflictException 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_service_catalog_appregistry import AsyncServiceCatalogAppRegistryClient


async def main():
    async with AsyncServiceCatalogAppRegistryClient() as service_catalog_app_registry:
        # Default: 3 attempts for every operation
        response = await service_catalog_app_registry.associate_attribute_group()

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

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

Metadata

Release files for capo-service-catalog-appregistry 0.1.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-service-catalog-appregistry 0.1.0
File Size Uploaded Provenance
capo_service_catalog_appregistry-0.1.0.tar.gz 79.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-service-catalog-appregistry 0.1.0
File Interpreter ABI Platform
capo_service_catalog_appregistry-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 256.8 kB

Release files / capo_service_catalog_appregistry-0.1.0.tar.gz

Download URL capo_service_catalog_appregistry-0.1.0.tar.gz
Size 79.2 kB
Tags Source
SHA-256 checksum
How to use checksums
42054a3dae55ccfe717e510406d91d843251b02b456b358c13b841a7836ee740
BLAKE2b-256 checksum
How to use checksums
bcc52f222ffcfccbf88691e6840edb0ab0c14ad06024104453de3a17ab50ace9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.20 {"installer":{"name":"uv","version":"0.12.20","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_service_catalog_appregistry-0.1.0-py3-none-any.whl

Download URL capo_service_catalog_appregistry-0.1.0-py3-none-any.whl
Size 177.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
47cfbb3cd33d073a426292e23c0bf089943f951070e5adc69f417b5b0a2331c0
BLAKE2b-256 checksum
How to use checksums
eef54dd38c9e525bacc08b861ee8e34258f33396b1a7eaab9aea71ae30c136b2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.20 {"installer":{"name":"uv","version":"0.12.20","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-service-catalog-appregistry 0.1.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