Skip to main content

Getting Started

Installation

pip install capo-migrationhubstrategy

Usage

from capo_migrationhubstrategy import AsyncMigrationHubStrategyClient


async def main():
    async with AsyncMigrationHubStrategyClient() as migration_hub_strategy:
        # Example: call the get_application_component_details operation
        response = await migration_hub_strategy.get_application_component_details()
        print(response["application_component_detail"])

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_migrationhubstrategy import AsyncMigrationHubStrategyClient


async def main():
    async with AsyncMigrationHubStrategyClient() as migration_hub_strategy:
        # Example: paginate over get_server_details
        async for item in migration_hub_strategy.iter_get_server_details():
            print(item)

Error Handling

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

from capo_migrationhubstrategy import AsyncMigrationHubStrategyClient
from capo_migrationhubstrategy.error import InternalServerException


async def main():
    async with AsyncMigrationHubStrategyClient() as migration_hub_strategy:
        try:
            await migration_hub_strategy.get_application_component_details()
        except InternalServerException 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_migrationhubstrategy import AsyncMigrationHubStrategyClient


async def main():
    async with AsyncMigrationHubStrategyClient() as migration_hub_strategy:
        # Default: 3 attempts for every operation
        response = await migration_hub_strategy.get_application_component_details()

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

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

Metadata

Release files for capo-migrationhubstrategy 0.3.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-migrationhubstrategy 0.3.0
File Size Uploaded Provenance
capo_migrationhubstrategy-0.3.0.tar.gz 106.8 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-migrationhubstrategy 0.3.0
File Interpreter ABI Platform
capo_migrationhubstrategy-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 347.2 kB

Release files / capo_migrationhubstrategy-0.3.0.tar.gz

Download URL capo_migrationhubstrategy-0.3.0.tar.gz
Size 106.8 kB
Tags Source
SHA-256 checksum
How to use checksums
1ac8d4abf7236a58afcf71302bf5b63cd6bf1321e590ac695055511829a59618
BLAKE2b-256 checksum
How to use checksums
d2ee079e5abde0480a52e061d8fbcac67f36e0e3d9c77776ab54f37c55837ae5
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_migrationhubstrategy-0.3.0-py3-none-any.whl

Download URL capo_migrationhubstrategy-0.3.0-py3-none-any.whl
Size 240.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fd421d6bf7cb2b5b36601496be901a952862e20a7dd4b1621a645fed51da39c6
BLAKE2b-256 checksum
How to use checksums
1b28ab5c6b05d1b798cbab30184c656d3166c2a776bbdeff4135d5cd2b27e490
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-migrationhubstrategy 0.3.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