Skip to main content

Getting Started

Installation

pip install capo-servicediscovery

Usage

from capo_servicediscovery import AsyncServiceDiscoveryClient


async def main():
    async with AsyncServiceDiscoveryClient() as service_discovery:
        # Example: call the create_http_namespace operation
        response = await service_discovery.create_http_namespace()
        print(response["operation_id"])

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_servicediscovery import AsyncServiceDiscoveryClient


async def main():
    async with AsyncServiceDiscoveryClient() as service_discovery:
        # Example: paginate over get_instances_health_status
        async for item in service_discovery.iter_get_instances_health_status():
            print(item)

Error Handling

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

from capo_servicediscovery import AsyncServiceDiscoveryClient
from capo_servicediscovery.error import DuplicateRequest


async def main():
    async with AsyncServiceDiscoveryClient() as service_discovery:
        try:
            await service_discovery.create_http_namespace()
        except DuplicateRequest 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_servicediscovery import AsyncServiceDiscoveryClient


async def main():
    async with AsyncServiceDiscoveryClient() as service_discovery:
        # Default: 3 attempts for every operation
        response = await service_discovery.create_http_namespace()

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

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

Metadata

Release files for capo-servicediscovery 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-servicediscovery 0.1.0
File Size Uploaded Provenance
capo_servicediscovery-0.1.0.tar.gz 120.8 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-servicediscovery 0.1.0
File Interpreter ABI Platform
capo_servicediscovery-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 391.6 kB

Release files / capo_servicediscovery-0.1.0.tar.gz

Download URL capo_servicediscovery-0.1.0.tar.gz
Size 120.8 kB
Tags Source
SHA-256 checksum
How to use checksums
fff7ab2661d267266731e301078872513fb53b0d761ad44b288a9ccc706a1c97
BLAKE2b-256 checksum
How to use checksums
f7712cb2d71a0b36b700ffca33b32c272c3f20bbdc9c9d491cc05c7e147445c7
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_servicediscovery-0.1.0-py3-none-any.whl

Download URL capo_servicediscovery-0.1.0-py3-none-any.whl
Size 270.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
24f9e88eacce11ccbbc0d221a190cf240783f369b110c399e7c573d54e8c2165
BLAKE2b-256 checksum
How to use checksums
ed543f2d74aaf51750c31cc97cc271dc6ee35a4617fc08c6a90bc7ba72f93017
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-servicediscovery 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