Skip to main content
Vintony HostPremium cloud

Managing Vintony with Terraform

Our Terraform provider, current resources, and example HCL.

3 min read

We maintain a Terraform provider at the `vintonyhost/vintony` registry path. Pin the version; the API is stable but the provider may add resources.

hcl
terraform {
  required_providers {
    vintony = { source = "vintonyhost/vintony", version = "~> 1.0" }
  }
}
provider "vintony" { token = var.vintony_token }
resource "vintony_vps" "web" {
  plan     = "vps-growth"
  region   = "lon1"
  image    = "ubuntu-24.04"
  hostname = "web-01"
  ssh_keys = [file("~/.ssh/id_ed25519.pub")]
}

Resources today: `vintony_vps`, `vintony_dedicated`, `vintony_domain`, `vintony_dns_record`, `vintony_api_token`. More are added as the underlying API endpoints stabilise.

State storage: standard Terraform remote backends work fine. Sensitive outputs (root credentials) are marked sensitive in the provider; they'll be redacted in `terraform output` unless explicitly requested.