Skip to main content

Getting Started

Installation

pip install capo-migrationhuborchestrator

Usage

from capo_migrationhuborchestrator import AsyncMigrationHubOrchestratorClient


async def main():
    async with AsyncMigrationHubOrchestratorClient() as migration_hub_orchestrator:
        # Example: call the list_tags_for_resource operation
        response = await migration_hub_orchestrator.list_tags_for_resource()
        print(response["tags"])

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_migrationhuborchestrator import AsyncMigrationHubOrchestratorClient


async def main():
    async with AsyncMigrationHubOrchestratorClient() as migration_hub_orchestrator:
        # Example: paginate over list_workflows
        async for item in migration_hub_orchestrator.iter_list_workflows():
            print(item)

Error Handling

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

from capo_migrationhuborchestrator import AsyncMigrationHubOrchestratorClient
from capo_migrationhuborchestrator.error import ResourceNotFoundException


async def main():
    async with AsyncMigrationHubOrchestratorClient() as migration_hub_orchestrator:
        try:
            await migration_hub_orchestrator.list_tags_for_resource()
        except ResourceNotFoundException 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_migrationhuborchestrator import AsyncMigrationHubOrchestratorClient


async def main():
    async with AsyncMigrationHubOrchestratorClient() as migration_hub_orchestrator:
        # Default: 3 attempts for every operation
        response = await migration_hub_orchestrator.list_tags_for_resource()

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

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

Metadata

Release files for capo-migrationhuborchestrator 0.2.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-migrationhuborchestrator 0.2.0
File Size Uploaded Provenance
capo_migrationhuborchestrator-0.2.0.tar.gz 105.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-migrationhuborchestrator 0.2.0
File Interpreter ABI Platform
capo_migrationhuborchestrator-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 345.0 kB

Release files / capo_migrationhuborchestrator-0.2.0.tar.gz

Download URL capo_migrationhuborchestrator-0.2.0.tar.gz
Size 105.2 kB
Tags Source
SHA-256 checksum
How to use checksums
e46752b6a5ab8a7b3c2c8c145ad17a9beb67937a229113988b90a626887f26f7
BLAKE2b-256 checksum
How to use checksums
8e7a9a4476e6963926ca458efb844fc9b11273208faf00ce4cdc5f4f5d88a620
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.21 {"installer":{"name":"uv","version":"0.12.21","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_migrationhuborchestrator-0.2.0-py3-none-any.whl

Download URL capo_migrationhuborchestrator-0.2.0-py3-none-any.whl
Size 239.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
89a7860071cb127adf16b1badccb4ac627fa1cdecb555ff35e01ea744c6a0e50
BLAKE2b-256 checksum
How to use checksums
4af11a9838035bc112a5757f76c4b4c9315879f56bf5e7efc2036d6553dcc38c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.21 {"installer":{"name":"uv","version":"0.12.21","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-migrationhuborchestrator 0.2.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