ccflow-http
ccflow models for HTTP
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, compatibilityHTTPResult,HTTPModel, templated path/query/header rendering, request explanation throughbuild_request, no-auth/bearer/API-key/basic auth helpers, JSON/text/bytes/CSV/gzip response parsing, HTTP status retry classification overccflowretry semantics, accepted error statuses returned as results instead of exceptions, retry event summaries on HTTP results,ccflow-etlExecutionPolicyrequest spacing,next_url/cursor/page/offset pagination, rate-limit header capture, redaction of secret query values (including the configuredapi_key_queryparameter) fromhttpx2request logs, request dumps, result URLs, retry events, and errors,HTTPDownloadModelfor streaming a response to a local file with size and SHA-256,HTTPArtifactCaptureModelfor storing a dated download plus a manifest through accflow-etlfile writer, and mockedhttpx2transport tests. - Partial: the shared execution policy is currently consumed inside
HTTPModelfor 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
ccflowfor callable model, context, and result interfaces. - Depends on
ccflowretry policy semantics andccflow-etlexecution 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.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ccflow_http-0.3.0.tar.gz | 21.3 kB | Without provenance | Details for ccflow_http-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ccflow_http-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for ccflow_http-0.3.0-py3-none-any.whl |
Total release size: 44.1 kB
Release files / ccflow_http-0.3.0.tar.gz
| Download URL | ccflow_http-0.3.0.tar.gz |
|---|---|
| Size | 21.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
072cb83a546e0321524a4b0873142b1a2899d9bef5be8efc23581e36e39a7cfc
|
|
BLAKE2b-256 checksum How to use checksums |
f8723b6d65b8f65708204f3ee3890192d59ea1d551afc28f2bb3481cedcdd39a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Release files / ccflow_http-0.3.0-py3-none-any.whl
| Download URL | ccflow_http-0.3.0-py3-none-any.whl |
|---|---|
| Size | 22.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f4f83576bb2675b94a4c6011bcf483ca4b72ce4c0ebf33b8a24dbb746c6fbf4c
|
|
BLAKE2b-256 checksum How to use checksums |
d9ff9b7f845e0aa76463d616c393529b78c9311acb90924c0810511e74cd15b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Security for ccflow-http 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.