Crate cloud_sdk

Expand description

no_std-first multi-provider cloud SDK for Rust.
Provider crates, explicit API domains, security-first release gates, and transport-free core types.

Crates.io | Docs.rs | Release Plan | Threat Model | Security

§cloud-sdk

cloud-sdk is a no_std-first Rust workspace for cloud provider SDKs. The first provider crate is cloud-sdk-hetzner, covering the Hetzner Cloud and DNS APIs. The default crates have no network client, TLS stack, async runtime, filesystem, clock, or secret-storage dependency. Transport and serde support will be admitted later behind explicit features or adapter crates.

The project target is a serious production-ready cloud-sdk foundation and Hetzner provider at 1.0.0, reached through small reviewed releases with test, security, dependency, and release evidence. Future provider crates can follow the same pattern, especially focused cloud and SaaS providers such as cloud-sdk-scaleway or cloud-sdk-ovh.

§Cost And Production Warning

Cloud APIs can create, modify, and delete billable resources. This SDK is built with careful review, tests, security gates, and release checks, but no SDK can guarantee that it is free from mistakes or that every provider-side API behavior is risk-free.

Before running code against a real cloud account, review the exact operations, inputs, permissions, and provider pricing yourself. You are responsible for the infrastructure actions you execute and for any costs, downtime, data loss, or configuration changes caused by those actions. If you find an SDK mistake, please report it so it can be fixed.

§Current Status

Status: v0.8.0 release candidate; pentest and retest complete.

Implemented now:

Rust workspace pinned to stable 1.96.1.
MSRV policy for Rust 1.90.0 through 1.96.1.
Edition 2024 and workspace resolver 3.
cloud-sdk provider-neutral crate.
cloud-sdk-hetzner provider crate with focused internal modules.
Initial Hetzner API surface partition for Cloud, DNS, security, and Storage Box resources.
Explicit placeholder crates for future Hetzner reqwest transport, testkit, and sanitization boundaries.
Local checks for formatting, linting, tests, no_std policy, modularity, and file length.
MIT OR Apache-2.0 license.
Security, implementation, release, modularity, supply-chain, and threat-model docs.
Official Hetzner Cloud/DNS and Storage Box spec source lock for v0.2.0.
Complete source-derived API matrix with 221 operations, owner modules, pagination, sorting, action behavior, deprecation status, and implementation status.
Local upstream lock validation for the pinned Hetzner spec URLs and hashes.
Hetzner API drift detection for added, removed, and changed operations and component schemas.
Core Hetzner request/response policy domains for endpoint paths, base URL selection, endpoint group base mapping, bounded query parameters, fixed-buffer percent encoding, labels, pagination, sorting, action status, API errors, and rate-limit metadata.
Read-only Hetzner catalog request primitives for locations, pricing, server types, load balancer types, ISOs, and public images.
Hetzner security request primitives for SSH key CRUD, certificate CRUD, and certificate retry action endpoints.
Hetzner server request primitives for server CRUD, metrics, and server action endpoint paths.
Hetzner server-adjacent request primitives for images, placement groups, primary IPs, and their v0.7 action paths.
Hetzner storage/IP request primitives for volumes, floating IPs, and their v0.8 action paths.

Not implemented yet:

No HTTP transport.
No token storage or secret manager integration.
No serde request/response models or body serialization.
No pagination iterator.
No retry, rate-limit, or action polling helper.
No generated response model.
No live Hetzner API tests.
No non-Hetzner providers yet. Smaller focused cloud and SaaS providers such as Scaleway and OVH are better future fits than hyperscaler-scale APIs, but no non-Hetzner provider is a 1.0 deliverable.
No Robot Webservice support. Robot is planned after the Hetzner Cloud/DNS provider reaches 1.0.0, likely as a 1.1.0 track exposed through cloud-sdk-hetzner.

§Trust Dashboard

Area	Status
License	`MIT OR Apache-2.0`
MSRV	Rust `1.90.0`
Pinned toolchain	Rust `1.96.1`
Default target	`no_std`
Default runtime dependencies	none in `cloud-sdk`; provider crates remain transport-free by default
Unsafe policy	first-party crates use `#![forbid(unsafe_code)]`
Default features	empty
Network defaults	none
Secret storage defaults	none
Release evidence	local gates, dependency policy, SBOM, pentest report before tags
Crate versions	tracked in `docs/CRATE_VERSION_MATRIX.md`
1.0 target	serious production-ready provider-neutral foundation plus Hetzner provider

§Provider Roadmap

Provider	Target Version	Crate
`Hetzner Cloud`	1.0.0	`cloud-sdk-hetzner`
`Hetzner Robot`	1.1.0	planned in `cloud-sdk-hetzner`

§Install

[dependencies]
cloud-sdk = "0.8.0"
cloud-sdk-hetzner = "0.8.0"

§Provider-Neutral Example

use cloud_sdk::{ApiFamily, Method, Provider};

let provider = Provider::Hetzner;
let family = ApiFamily::Cloud;
let method = Method::Get;

assert_eq!(provider, Provider::Hetzner);
assert_eq!(family, ApiFamily::Cloud);
assert_eq!(method, Method::Get);

§Fixed Buffer Example

use cloud_sdk::buffer::write_query_u64;

let mut output = [0u8; 8];
let mut len = 0;
let mut first = true;
write_query_u64(&mut output, &mut len, &mut first, "page", 0, ())?;

let query = output
    .get(..len)
    .and_then(|bytes| core::str::from_utf8(bytes).ok());
assert_eq!(query, Some("page=0"));

§JSON String Example

use cloud_sdk::buffer::write_json_string;

let mut output = [0u8; 48];
let mut len = 0;
write_json_string(&mut output, &mut len, "line\n\"quoted\"", ())?;

let value = output
    .get(..len)
    .and_then(|bytes| core::str::from_utf8(bytes).ok());
assert_eq!(value, Some("\"line\\n\\\"quoted\\\"\""));

§Workspace Crates

Crate	Default `std`?	Purpose
`cloud-sdk`	no	Provider-neutral domains and shared SDK foundation.
`cloud-sdk-hetzner`	no	Main Hetzner documentation and provider crate with internal `cloud`, `dns`, `security`, and `storage` modules.
`cloud-sdk-hetzner-reqwest`	no	Future optional reqwest transport adapter; no transport dependency admitted yet.
`cloud-sdk-hetzner-testkit`	no	Future mock transport, fixtures, and adversarial API response helpers.
`cloud-sdk-hetzner-sanitization`	no	Future optional token/secret sanitization helpers.

The root README documents the workspace and release process. Crate-local README files document the crate-specific role and examples. For Hetzner-specific usage, start with cloud-sdk-hetzner.

Hetzner endpoint modules live inside the provider crate:

crates/cloud-sdk-hetzner/src/
  actions.rs
  endpoint.rs
  labels.rs
  pagination.rs
  rate_limit.rs
  request.rs
  response.rs
  cloud/catalog.rs
  cloud/
  dns/
  security/
  storage/

§API Scope

The first planning pass covers the Hetzner Cloud API reference at https://docs.hetzner.cloud/reference/cloud, including overview material for authentication, query parameters, errors, actions, labels, pagination, rate limiting, server metadata, sorting, and deprecation notices.

Robot Webservice support is intentionally post-1.0. It uses a different API shape, authentication model, and request encoding than the Cloud/DNS API. The planned direction is to expose it through cloud-sdk-hetzner after 1.0, without letting Robot-specific behavior weaken the default Cloud SDK design.

Endpoint groups scheduled for the SDK:

Area	Groups
Cross-resource	actions
Servers	servers, server actions, server types, images, image actions, ISOs, placement groups, primary IPs, primary IP actions
Storage	volumes, volume actions
IPs	floating IPs, floating IP actions
Network edge	firewalls, firewall actions, load balancers, load balancer actions, load balancer types, networks, network actions
DNS	zones, zone actions, zone RRSets, zone RRSet actions
Security	certificates, certificate actions, SSH keys
Storage Boxes	storage boxes, storage box actions, storage box subaccounts
Catalog and billing	locations, pricing

The v0.2.0 planning pass source-locked the official machine-readable specs:

Cloud and DNS: https://docs.hetzner.cloud/cloud.spec.json
Storage Boxes: https://docs.hetzner.cloud/hetzner.spec.json

docs/API_MATRIX.md tracks all 221 discovered operations. Deprecated operations remain listed for drift tracking, but are marked deferred-deprecated until the SDK has an explicit compatibility policy.

Before changing endpoint models, run:

scripts/check_hetzner_api_drift.py --fetch

That compares the current upstream specs with the locked operation and schema fingerprints in docs/API_FINGERPRINTS.tsv and docs/API_SCHEMA_FINGERPRINTS.tsv.

Do not refresh lock files directly from a drift report. First review the upstream changes and update the pinned spec hashes in the source-lock evidence. Then refresh the fingerprints during the reviewed source-lock pass:

scripts/check_hetzner_api_drift.py --fetch --write-lock --accept-lock-refresh

The write path verifies fetched spec bytes against the pinned SHA-256 values before overwriting the fingerprint files.

§Rust Version Support

The minimum supported Rust version is Rust 1.90.0. Development uses the pinned stable Rust 1.96.1 until the toolchain policy is updated.

Compatibility evidence for 0.8.0:

Rust	Local Evidence
`1.90.0`	`cargo +1.90.0 check --workspace --all-features`
`1.91.0`	`cargo +1.91.0 check --workspace --all-features`
`1.92.0`	`cargo +1.92.0 check --workspace --all-features`
`1.93.0`	`cargo +1.93.0 check --workspace --all-features`
`1.94.0`	`cargo +1.94.0 check --workspace --all-features`
`1.95.0`	`cargo +1.95.0 check --workspace --all-features`
`1.96.0`	`cargo +1.96.0 check --workspace --all-features`
`1.96.1`	`scripts/checks.sh`

§Checks

scripts/checks.sh
scripts/release_0_1_gate.sh
scripts/check_hetzner_upstream.sh --local-only
scripts/check_hetzner_api_drift.py --fetch
scripts/release_0_2_gate.sh
scripts/release_0_3_gate.sh
scripts/release_0_4_gate.sh
scripts/release_0_5_gate.sh
scripts/release_0_6_gate.sh
scripts/release_0_7_gate.sh
scripts/release_0_8_gate.sh

Modules§

buffer: no_std fixed-buffer writing helpers for provider crates.

Enums§

ApiFamily: Provider API family.
Method: HTTP method for a provider operation.
Provider: Cloud provider namespace.

Crate cloud_sdk

Crate cloud_sdk Copy item path

§cloud-sdk

§Cost And Production Warning

§Current Status

§Trust Dashboard

§Provider Roadmap

§Install

§Provider-Neutral Example

§Fixed Buffer Example

§JSON String Example

§Workspace Crates

§API Scope

§Rust Version Support

§Checks

Modules§

Enums§

Crate cloud_sdk