Skip to main content

Getting Started

Installation

pip install capo-resource-groups-tagging-api

Usage

from capo_resource_groups_tagging_api import AsyncResourceGroupsTaggingAPIClient


async def main():
    async with AsyncResourceGroupsTaggingAPIClient() as resource_groups_tagging_api:
        # Example: call the describe_report_creation operation
        response = await resource_groups_tagging_api.describe_report_creation()
        print(response["status"])

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_resource_groups_tagging_api import AsyncResourceGroupsTaggingAPIClient


async def main():
    async with AsyncResourceGroupsTaggingAPIClient() as resource_groups_tagging_api:
        # Example: paginate over get_compliance_summary
        async for item in resource_groups_tagging_api.iter_get_compliance_summary():
            print(item)

Error Handling

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

from capo_resource_groups_tagging_api import AsyncResourceGroupsTaggingAPIClient
from capo_resource_groups_tagging_api.error import ConstraintViolationException


async def main():
    async with AsyncResourceGroupsTaggingAPIClient() as resource_groups_tagging_api:
        try:
            await resource_groups_tagging_api.describe_report_creation()
        except ConstraintViolationException 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_resource_groups_tagging_api import AsyncResourceGroupsTaggingAPIClient


async def main():
    async with AsyncResourceGroupsTaggingAPIClient() as resource_groups_tagging_api:
        # Default: 3 attempts for every operation
        response = await resource_groups_tagging_api.describe_report_creation()

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

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

Metadata

Release files for capo-resource-groups-tagging-api 0.5.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-resource-groups-tagging-api 0.5.0
File Size Uploaded Provenance
capo_resource_groups_tagging_api-0.5.0.tar.gz 83.9 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-resource-groups-tagging-api 0.5.0
File Interpreter ABI Platform
capo_resource_groups_tagging_api-0.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 222.0 kB

Release files / capo_resource_groups_tagging_api-0.5.0.tar.gz

Download URL capo_resource_groups_tagging_api-0.5.0.tar.gz
Size 83.9 kB
Tags Source
SHA-256 checksum
How to use checksums
4f094aa2c79e7292ceed5d480a905e0b456de9caa1f30dec11d952042e57dedb
BLAKE2b-256 checksum
How to use checksums
969b9094d45ae232af835c834dacd2b1a776ed78d1459e48da006cc3e588bab1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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_resource_groups_tagging_api-0.5.0-py3-none-any.whl

Download URL capo_resource_groups_tagging_api-0.5.0-py3-none-any.whl
Size 138.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7222bd02a27b0f2e760ea78a37cd7f77f18732d8824c998a449f32b468bfc7be
BLAKE2b-256 checksum
How to use checksums
71207240157b2adcd12ade0771d6114df9bff1809f7eb87250442f68f2bf9a11
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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-resource-groups-tagging-api 0.5.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