Vultr Terraform Provider

The vultr_database_topic resource allows you to create, read, modify, and delete topics for a managed database on your Vultr account.

Important Note: Updating the database_id will trigger a force new operation, meaning the existing topic will be destroyed and a new one created. This is because a database topic cannot be moved from one managed database to another.

resource "vultr_database_topic" "my_database_topic" {
	database_id = vultr_database.my_database.id
	name = "my_database_topic"
	partitions = "3"
	replication = "2"
	retention_hours = "120"
	retention_bytes = "-1"
}

The vultr_user resource allows you to create, read, modify, and delete users within your Vultr account via Terraform. You can define basic user credentials or create highly privileged users by specifying Access Control Lists (ACLs), assigning them to specific groups or roles, and designating them as service users.

resource "vultr_user" "my_user" {
	name = "my user"
	email = "user@vultr.com"
	password = "myP@ssw0rd"
	api_enabled = true
}

The vultr_bare_metal_server resource allows you to create, read, modify, and delete bare metal servers on your Vultr account using Terraform. You can specify the hardware plan, region, operating system, and various networking and configuration options like IPv6, SSH keys, and user data.

resource "vultr_bare_metal_server" "my_server" {
	plan = "vbm-4c-32gb"
	region = "ewr"
	os_id = 1743
}

The vultr_database resource allows you to create, read, modify, and delete managed databases on your Vultr account. This includes support for various engines like PostgreSQL, MySQL, Kafka, and Valkey.

Important Note on Engine Updates: Updating the database_engine will trigger a force new (destruction and recreation) because Vultr does not support changing the engine type of an existing database. However, updating the database_engine_version is supported if an upgrade is available.

resource "vultr_database" "my_database" {
	database_engine = "pg"
	database_engine_version = "15"
    region = "ewr"
    plan = "vultr-dbaas-startup-cc-1-55-2"
    label = "my_database_label"
}

The vultr_vpc resource allows you to create, read, and delete Virtual Private Clouds (VPCs) on your Vultr account. You can either let Vultr automatically generate a CIDR block or specify your own IPv4 subnet and mask.

resource "vultr_vpc" "my_vpc" {
	description = "my vpc"
	region = "ewr"
}

In the V2 provider, all resource IDs are now UUIDs. References to previous ID formats are no longer supported. This applies to the following resource types:

• Instances
• Bare Metal
• Block Storage
• Object Storage
• Reserved IP
• Load Balancer
• Snapshots & Backups
• DNS Records
• ISOs (Private & Public)
• Private Networks
• Startup Scripts
• SSH Keys
• Firewall Groups
• Container Registry

Actionable Requirements:

• Data Sources: When filtering by ID or any other resource ID, you must use the resource's UUID.
• Resource Arguments: Any argument that accepts another resource as a reference (e.g., snapshot_id when creating an instance) must be provided as a UUID.

The vultr_database_connection_pool resource allows you to create, read, modify, and delete connection pools for PostgreSQL managed databases on Vultr.

Important Note on Updates: Updating the database_id or the name will trigger a force new operation (the resource will be destroyed and recreated). This is because connection pools cannot be moved between managed databases and pool names are immutable once created.

resource "vultr_database_connection_pool" "my_database_connection_pool" {
	database_id = vultr_database.my_database.id
	name = "my_database_connection_pool_name"
	database = "defaultdb"
	username = "vultradmin"
	mode = "transaction"
	size = 3
}

You can import an existing object storage subscription into your Terraform state using its unique ID.

terraform import vultr_object_storage.my_s3 0e04f918-575e-41cb-86f6-d729b354a5a1

To import an existing node pool, you must provide both the Cluster UUID and the Node Pool UUID. The import format requires a space-delimited string where the first ID is the clusterID and the second is the nodePoolID.

# Format: "clusterID nodePoolID"
terraform import vultr_kubernetes_node_pools.my-k8s-np "7365a98b-5a43-450f-bd27-d768827100e5 ec330340-4f50-4526-858f-a39199f568ac"

You can import an existing Snapshot from URL into your Terraform state using its Snapshot ID.

terraform import vultr_snapshot_from_url.my_snapshot <SNAPSHOT_ID>

terraform import vultr_snapshot_from_url.my_snapshot e60dc0a2-9313-4bab-bffc-57ffe33d99f6

You can bring an existing Vultr Startup Script under Terraform management by importing it using its unique ID via the terraform import command.

terraform import vultr_startup_script.my_script ff8f36a8-eb86-4b8d-8667-b9d5459b6390