Skip to main content

ccflow-http

ccflow models for HTTP

Build Status codecov License PyPI

Overview

ccflow-http provides public, domain-neutral HTTP callable models for ccflow workflows. It should own request configuration, auth strategies, request templating, pagination, response parsing, timeout handling, retry/rate-limit integration, and HTTP result metadata.

It should not contain provider-specific endpoint catalogs. Domain packages can configure or subclass these generic models for particular APIs.

Current Status

  • Implemented: HTTPConfig, HTTPAuth, HTTPContext, HTTPRequestContext, HTTPRequest, HTTPRetryPolicy, HTTPResponseResult, compatibility HTTPResult, HTTPModel, templated path/query/header rendering, request explanation through build_request, no-auth/bearer/API-key/basic auth helpers, JSON/text/bytes/CSV/gzip response parsing, HTTP status retry classification over ccflow retry semantics, accepted error statuses returned as results instead of exceptions, retry event summaries on HTTP results, ccflow-etl ExecutionPolicy request spacing, next_url/cursor/page/offset pagination, rate-limit header capture, a configurable RedactionPolicy (HTTPModel.redaction: exact names, substrings, and patterns, with auth header and query names added automatically) that masks secret header and query values in httpx2 request logs, request dumps, result URLs and headers, retry events, and errors, HTTPDownloadModel for streaming a response to a local file with size and SHA-256, HTTPArtifactCaptureModel for storing a dated download plus a manifest through a ccflow-etl file writer, and mocked httpx2 transport tests.
  • Partial: the shared execution policy is currently consumed inside HTTPModel for sequential request spacing; broader evaluator-level concurrency coordination still belongs in evaluator integrations.
  • Missing: broader integration examples and provider-specific subclasses/configs in downstream packages.

Dependency Contract

  • Depends on ccflow for callable model, context, and result interfaces.
  • Depends on ccflow retry policy semantics and ccflow-etl execution policy models.
  • Must not depend on finance packages or application-specific packages.

Test Convention

Default tests should use mocked httpx2 transports or local fixtures. They should not require live network calls or provider credentials.

Metadata

Release files for ccflow-http 0.4.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ccflow-http 0.4.1
File Size Uploaded Provenance Actions
ccflow_http-0.4.1.tar.gz 22.8 kB Without provenance Details for ccflow_http-0.4.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for ccflow-http 0.4.1
File Interpreter ABI Platform Actions
ccflow_http-0.4.1-py3-none-any.whl Python 3 none any Details for ccflow_http-0.4.1-py3-none-any.whl

Total release size: 47.1 kB

Release files / ccflow_http-0.4.1.tar.gz

Download URL ccflow_http-0.4.1.tar.gz
Size 22.8 kB
Tags Source
SHA-256 checksum
How to use checksums
99d2bdeaac1faff9bf6f3cd7f92acad6d5afd0ccdf0a4ecde0bccf2c416955d8
BLAKE2b-256 checksum
How to use checksums
25640d651d1e90f13ce066e4b28ac96fca6bcda299215c359e9dbca6c50fea7b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.15

Release files / ccflow_http-0.4.1-py3-none-any.whl

Download URL ccflow_http-0.4.1-py3-none-any.whl
Size 24.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e46bc591e484649491a34109c8e48ec95ea543ff106fc97a42bbf24b73b8fa04
BLAKE2b-256 checksum
How to use checksums
8d1f7430542d405d023c88e8917078a1e4917a7ce71665f77dd568f19526b2e5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.15

Security for ccflow-http 0.4.1

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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