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.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-resource-groups-tagging-api 0.2.0
File Size Uploaded Provenance
capo_resource_groups_tagging_api-0.2.0.tar.gz 83.5 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 221.1 kB

Release files / capo_resource_groups_tagging_api-0.2.0.tar.gz

Download URL capo_resource_groups_tagging_api-0.2.0.tar.gz
Size 83.5 kB
Tags Source
SHA-256 checksum
How to use checksums
e6d29fac89301183d5caebf9b4de4c00627e3f4c5bcbe07698268e469fc27d2f
BLAKE2b-256 checksum
How to use checksums
e72da59a1d2c1a4af125a44022e8d5f5d8a6c4529677a8305e41b3ce1cd0acd4
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_resource_groups_tagging_api-0.2.0-py3-none-any.whl

Download URL capo_resource_groups_tagging_api-0.2.0-py3-none-any.whl
Size 137.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
449196b86640f87dcc5c1b3ca208fdb6e2d21dd0e2b2cf647afb43e0f82440cc
BLAKE2b-256 checksum
How to use checksums
8c80c06fa8351340ec5866863721285687eeb36789d0d7dbb71c214e0dc5b0b8
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-resource-groups-tagging-api 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