Skip to main content

Getting Started

Installation

pip install capo-network-firewall

Usage

from capo_network_firewall import AsyncNetworkFirewallClient


async def main():
    async with AsyncNetworkFirewallClient() as network_firewall:
        # Example: call the accept_network_firewall_transit_gateway_attachment operation
        response = await network_firewall.accept_network_firewall_transit_gateway_attachment()
        print(response["transit_gateway_attachment_id"])

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_network_firewall import AsyncNetworkFirewallClient


async def main():
    async with AsyncNetworkFirewallClient() as network_firewall:
        # Example: paginate over get_analysis_report_results
        async for item in network_firewall.iter_get_analysis_report_results():
            print(item)

Error Handling

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

from capo_network_firewall import AsyncNetworkFirewallClient
from capo_network_firewall.error import InternalServerError


async def main():
    async with AsyncNetworkFirewallClient() as network_firewall:
        try:
            await network_firewall.accept_network_firewall_transit_gateway_attachment()
        except InternalServerError 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_network_firewall import AsyncNetworkFirewallClient


async def main():
    async with AsyncNetworkFirewallClient() as network_firewall:
        # Default: 3 attempts for every operation
        response = await network_firewall.accept_network_firewall_transit_gateway_attachment()

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

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

Metadata

Release files for capo-network-firewall 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-network-firewall 0.3.0
File Size Uploaded Provenance
capo_network_firewall-0.3.0.tar.gz 256.8 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 950.4 kB

Release files / capo_network_firewall-0.3.0.tar.gz

Download URL capo_network_firewall-0.3.0.tar.gz
Size 256.8 kB
Tags Source
SHA-256 checksum
How to use checksums
1e06ff924e78ca1761f1e6ab7b3efaf2d063341f09996d7b574f645edad92759
BLAKE2b-256 checksum
How to use checksums
7421266b8aafbad4ba52a1a8e5ed637310cde4387e476edc3472030e38a6a14d
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_network_firewall-0.3.0-py3-none-any.whl

Download URL capo_network_firewall-0.3.0-py3-none-any.whl
Size 693.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
db189662fb0b1cf0f8b32a102dbbbcb2b114e76ca8c1f6172d5cbc5c8e21d8aa
BLAKE2b-256 checksum
How to use checksums
5fc81cba95b87d9f31268ccf48370a3bd6b2e4e3bb0374fe35769c3f769a3e92
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-network-firewall 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