tento-deploy

tento-deploy owns cloud instance provisioning, infrastructure verification, and deployment-oriented platform clients.

Public surface

• core::{Platform, Environment, PlatformOps, ProvisionOpts, ServerInstance} defines provider-independent instance operations.
• aws::{AwsDeployClient, ensure_infrastructure} is available behind the aws feature.
• gcp::GcpDeployClient is available behind the gcp feature.
• hcloud::HetznerDeployClient is available behind the hetzner feature.
• ansible contains inventory and playbook runner helpers.
• sync::infra verifies checked-in infrastructure config against live state.
• gcp::billing owns budget config drift, lock files, and apply operations.

Feature boundaries

Provider SDKs are feature-gated so callers can compile only the platform they need. Shared lifecycle concepts should live under core; provider-specific request/response types and API behavior should stay under aws, gcp, or hcloud.

Scripts and fleet commands should call PlatformOps or provider clients rather than using cloud SDKs directly. That keeps TTL handling, tags, and inventory expectations centralized.