HashiCorp Configuration Language (HCL)

HashiCorp Configuration Language (HCL) is a tool developed by HashiCorp, tailored for defining infrastructure configurations with a syntax that balances human readability and machine parsability. It's designed for use in provisioning and managing infrastructure across various cloud platforms and services, making it an invaluable asset in the realm of infrastructure as code (IaC). HCL is prominently featured in HashiCorp's suite of tools, including Terraform, Vault, and Nomad, each serving unique roles in infrastructure provisioning, secrets management, and application deployment, respectively.

HCL's Design and Syntax

At its core, HCL's design philosophy centers on simplicity and readability, catering to both newcomers and experienced practitioners in the infrastructure domain. It employs a declarative syntax, focusing on the desired end-state of the infrastructure rather than the steps to achieve it. This approach simplifies infrastructure management by abstracting the complexity involved in reaching the desired state.

HCL syntax is structured around blocks and attributes, with blocks defining configuration objects (like a resource in Terraform) and attributes specifying the properties of these objects. Comments can be integrated seamlessly, enhancing code readability and maintenance.

Cross-Cloud Examples

To illustrate the versatility and utility of HCL across different cloud environments, let's examine how it is used to define infrastructure components in AWS, Azure, and GCP:

AWS EC2 Instance

resource "aws_instance" "example" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
}

‍

This snippet demonstrates the definition of an AWS EC2 instance, specifying the Amazon Machine Image (AMI) and instance type.

Azure Virtual Machine

resource "azurerm_virtual_machine" "example" {
  name                  = "examplevm"
  location              = "East US"
  resource_group_name   = "example-resources"
  vm_size               = "Standard_DS1_v2"

  storage_os_disk {
    name              = "myosdisk"
    caching           = "ReadWrite"
    create_option     = "FromImage"
    managed_disk_type = "Standard_LRS"
  }

  os_profile {
    computer_name  = "hostname"
    admin_username = "adminuser"
    admin_password = "AdminPassword123!"
  }

  os_profile_linux_config {
    disable_password_authentication = false
  }
}

Here, an Azure VM is defined, including its location, VM size, storage configurations, and OS profile.

GCP Compute Engine Instance Example 

resource "google_compute_instance" "example" {
  name         = "example-instance"
  machine_type = "f1-micro"
  zone         = "us-central1-a"

  boot_disk {
    initialize_params {
      image = "debian-cloud/debian-9"
    }
  }

  network_interface {
    network = "default"
    access_config {
      // Ephemeral IP
    }
  }

  metadata = {
    foo = "bar"
  }
}

This snippet outlines the creation of a GCP Compute Engine instance, specifying its machine type, zone, boot disk configuration, and network interface.

Conclusion

HCL's consistent syntax and human-centric design philosophy make it a powerful tool for defining and managing infrastructure across multiple cloud platforms. Whether provisioning an EC2 instance on AWS, configuring a VM in Azure, or deploying a Compute Engine instance on GCP, HCL streamlines the process. Its integration with the HashiCorp suite enhances its utility, allowing for seamless infrastructure provisioning, secrets management, and application deployment. The ability to use a single language across diverse cloud ecosystems simplifies multi-cloud infrastructure management, making HCL an indispensable tool in modern cloud strategies.

‍