Five project-local skills manage Hivelocity using Bash, jq, curl or wget, and Terraform. hivelocity.toml stores desired state, remote IDs, observations, audits, and execution receipts. Live changes require approval of the exact plan.
bin/hv validate
bin/hv api list
bin/hv api list VPS
bin/hv api describe get_vps_resource
# Load HIVELOCITY_API_KEY from your secrets manager before making live queries.
bin/hv api read get_vps_resource
bin/hv sync
bin/hv auditDependencies: Bash 4+, jq 1.6+, flock (util-linux), POSIX/coreutils utilities, Terraform >=1.5 and <2, and curl or GNU wget. A Linux environment is recommended. HV_HTTP_CLIENT=wget forces the alternative HTTP client. Python is not required to run the tools.
The skills are hivelocity-ssot, hivelocity-inventory, hivelocity-api, hivelocity-terraform, and hivelocity-audit. Their source files live in skills/; discovery links are in .agents/skills/, within this project only.
| Coverage | Implementation |
|---|---|
| 261 operations across 34 API v2 groups | Official Swagger catalog, queries, validation, and contract-based execution |
| Bare metal servers, SSH keys, VLANs | Native adapters using the official Terraform provider 0.7.9 |
| VPS, DNS, IPs, volumes, snapshots, permissions, billing, webhooks, and other groups | ensure/once API contracts using terraform_data and shell scripts |
| Auditing | Native inventory and verification predicates defined for API operations |
| Recovery | Regeneration from TOML, server/VLAN imports, verified SSH state restoration, and operation receipts |
Catalog coverage does not mean 261 specialized workflows or production tests. The specification was downloaded from https://core.hivelocity.net/api/v2/swagger.json on 2026-09-13. The complete specification is retained for inspecting parameters and payloads. Operations outside the native adapters need a specification and, for convergence, a check appropriate to their semantics.
Read the SSOT format and operational examples and recovery procedures. Do not store API keys, passwords, or private SSH keys in the TOML file. Local state and plans may also contain sensitive data and are stored under .hivelocity/ with restrictive permissions.
Tests that require neither an account nor network access:
tests/run.shThe tests use simulated HTTP responses and Terraform behavior to verify repetition, errors, approval, locking, and recovery. The generated configuration was also validated with the real Terraform provider; no resources were applied in Hivelocity.
