Crate cloud_sdk_reqwest 

optional provider-neutral reqwest boundary for cloud-sdk.
Provider crates, explicit API domains, security-first release gates, and transport-free core types.

cloud-sdk crate | Docs.rs | Release Plan | Threat Model | Security

cloud-sdk-reqwest

Optional provider-neutral transport-adapter boundary for the main cloud-sdk workspace and cloud-sdk crate.

This crate exists so one future reviewed reqwest adapter can serve every cloud provider without adding transport dependencies to provider crates. It intentionally does not depend on reqwest yet.

Most users should start with:

[dependencies]
cloud-sdk = "0.15.0"

Use this crate only when the release notes say a transport adapter has been admitted.

Current Example

use cloud_sdk_reqwest::ReqwestAdapterStatus;

assert_eq!(
    ReqwestAdapterStatus::DependencyNotAdmitted,
    ReqwestAdapterStatus::DependencyNotAdmitted,
);

Admission Requirements

Before a real reqwest dependency is admitted, the workspace must review:

• HTTP client version, license, features, and maintenance status;
• TLS policy;
• timeout and retry behavior;
• authentication header redaction;
• authority-preserving base URL and origin-form target composition without scheme-relative // replacement or generic Url::join ambiguity;
• final outbound scheme, host, and port verification before attaching an authentication header;
• default feature impact;
• mock and live-test strategy.

Provider crates retain ownership of authentication, base URLs, request models, response interpretation, and provider-specific errors. This crate must not branch on provider names.

Enums

ReqwestAdapterStatus

Provider-neutral transport adapter readiness state.