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.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-migrationhuborchestrator 0.4.0
File Size Uploaded Provenance
capo_migrationhuborchestrator-0.4.0.tar.gz 105.4 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 345.5 kB

Release files / capo_migrationhuborchestrator-0.4.0.tar.gz

Download URL capo_migrationhuborchestrator-0.4.0.tar.gz
Size 105.4 kB
Tags Source
SHA-256 checksum
How to use checksums
d1abd584451ca0c42461b98c39d19517f445077b5da96f7764299ce21114384a
BLAKE2b-256 checksum
How to use checksums
2760ef2df74464b8b58e7ceb16d31e73df828ba5b5445e19807b98b2e35f4906
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","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.4.0-py3-none-any.whl

Download URL capo_migrationhuborchestrator-0.4.0-py3-none-any.whl
Size 240.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
334e8a2d05c1fb7c217f3835c52ef78352f96963bee72cdab86f7f28916b1f40
BLAKE2b-256 checksum
How to use checksums
6cfaffbd13ad5f1c984afe4f521f992268855bf2e272be5d61a74116d2bbe8da
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","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.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