Terraform Provider Hivelocity

• Terraform Website: https://www.terraform.io
• Hivelocity Website: https://hivelocity.net

Requirements

• Terraform 0.13.x
• Go 1.15+ (to build the provider plugin)

Official Documentation

For a more comprehensive documentation, including examples for every resource and data-source supported by the provider, please check:

• https://registry.terraform.io/providers/hivelocity/hivelocity/latest/docs

Example Usage

You may set the environment variable HIVELOCITY_API_KEY instead of setting it on the provider itself.

terraform {
  required_providers {
    hivelocity = {
      version  = "<VERSION>"
      source   = "hivelocity/hivelocity"
    }
  }
}

provider "hivelocity" {
  api_key=<YOUR-API-KEY>
}

// Find first in stock product with 16GB of memory in Tampa.
data "hivelocity_product" "tampa_product" {
  first = true

  filter {
    name   = "product_memory"
    values = ["16GB"]
  }

  filter {
    name   = "data_center"
    values = ["TPA1"]
  }

  filter {
    name   = "stock"
    values = ["limited", "available"]
  }
}

// Create a SSH Key
resource "hivelocity_ssh_key" "my_ssh_key" {
  name       = "This is my Terraform SSH Key"
  public_key = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDYYGqXPIJ1yQ7pMTSmdB+LrjvnPh2jSJewvinxYwuk/CBvbsUgFxOTBtjzfU0kHIlo5QyIhJ7tjh8PhT8LdJPGB86ItwTg3Lmt1q5UFxbHmZ0kPmmzaDI/9aakOal3P93D14HDCzBnkTHfC8/JZ5JpDxp86XM+gWQ9sFMkLx83ZOwONNu3E8PowTEpsp0jMx2B2aFeSM+T4bLkJJQtA5Cp6lgRAc5AklXaqmpdAil/fIL/+gvRf8kJIccAe/2oVj4flaMK7mgZ39qhzYYUjTEokEYvJf17QbdtFTxxtIQ+hTxzKzwT6p8cMu6DNQLfq6oxzbuBVGTvKD79MR5vjx+RNpaIru8wzIspHTez9eGDzdR0316GWDcxmMwVIDMM+3pjopDJV6DILfs6hVlAuH11yCX8YwwGHYpsdzLLd00FEEaGLGVRDr/hvduZ1caQIvdNln6Gr7k6W51U1VTC3NRq49yoxYSsXxn30PfTe2IxFaZyhQXHunCLaMCF+TrAOc0= [email protected]"
}

// Provision your devices with CentOS 7.
resource "hivelocity_bare_metal_device" "webserver" {
  product_id        = data.hivelocity_product.tampa_product.product_id
  os_name           = "CentOS 7.x"
  location_name     = data.hivelocity_product.tampa_product.data_center
  hostname          = "webserver.terraform.test"
  tags              = ["hello", "world"]
  script            = file("${path.module}/cloud_init_example.yaml")
  public_ssh_key_id = hivelocity_ssh_key.my_ssh_key.ssh_key_id
}

resource "hivelocity_bare_metal_device" "database" {
  product_id        = data.hivelocity_product.tampa_product.product_id
  os_name           = "CentOS 7.x"
  location_name     = data.hivelocity_product.tampa_product.data_center
  hostname          = "database.terraform.test"
  tags              = ["hello", "world"]
  script            = file("${path.module}/cloud_init_example.yaml")
  public_ssh_key_id = hivelocity_ssh_key.my_ssh_key.ssh_key_id
}

// Create a VLAN connecting servers
resource "hivelocity_vlan" "private_vlan" {
  device_ids    = [
      hivelocity_bare_metal_device.webserver.device_id,
      hivelocity_bare_metal_device.database.device_id,
  ]
}

The above provider will deploy and provision 2 units of the first found in stock (limited or available) device with 16GB of memory in the TPA1. They will be provisioned with CentOS7.x as the OS and received the tags hello and world. The hostname will be set to webserver.terraform.test for the first device and database.terraform.test for the second. Both will use a cloud-init user-data script to be executed on the device first boot.

Cloud-init script start with #cloud-init, must be a valid YAML script. Post-install script start with #!/bin/bash. Cloud-init or Post-install script just can be used with OS Ubuntu and Centos.

The VLAN resource creates an isolated network connection between devices, and it can be used by the user to establish a private network. The current implementation requires all devices to be located in the same facility.

Note: all these values can be changed from the portal, which could make terraform states get out of sync. We are working on a solution to help users avoid this issue.

Filtering

All data sources are filterable. You may create as many filters as you like as demonstrated above. The data source will return the value that matches all filters.

data "hivelocity_product" "tampa_product" {
  first = true

  filter {
    name   = "location"
    values = ["TPA1", "TPA2"]
  }
}

The above config has a single filter. The initial thing you will notice is the first = true variable. This means that if our filters match multiple objects return the first object that matched. If you want Terraform to throw an error when multiple objects are matched set first = false. Next the provider will look all hivelocity_products that are available and return the first product who's location is either TPA1 or TPA2

data "hivelocity_device" "ip_filter" {
  first = false

  filter {
    name   = "ip_addresses"
    values = ["66.165.245.226", "66.165.245.226"]
  }
}

Filters also work with fields that are arrays. In the above example the ip_addresses field returns an array of ip addresses. The filter will check if 66.165.245.226 or 66.165.245.225 is in the ip_addresses array.

You can pass strings, integers, or booleans to the values array on the filter. The type must match the returned type of the data source schema.

How to test Cloud-Init script locally

Please see https://api-docs.hivelocity.net/cloud-init-test

Developing the provider

Please see https://github.com/hivelocity/terraform-provider-hivelocity/blob/main/CONTRIBUTING.md