terraform VS hcl

2. Terraform (hashicorp/terraform) – Infrastructure as Code

Terraform is used to manage infrastructure. You can define your servers, databases, and networks in code, and Terraform will create them for you. It’s like DevOps magic. Written in Go.

Terraform: https://developer.hashicorp.com/terraform

Terraform or OpenTofu for infra as code

For more information on Docker, you can refer to the official Docker documentation and explore relevant open-source projects on Docker's GitHub. Additionally, for Terraform-related resources, check out the official Terraform documentation and Terraform GitHub.

In this post, I will share WebRTC.ventures' best practices in automating the deployment of AI-powered voice assistants for Amazon Connect, moving beyond manual, click-by-click setups to a robust, scalable Infrastructure as Code (IaC) approach. We’ll explore how to manage both static and dynamic resources, leverage tools like Terraform and AWS Serverless Application Model (SAM), and even set up an automated deployment pipeline using Github Actions to deploy your conversational IVR solutions efficiently.

We manage infrastructure with Terraform and lean heavily on GitHub Actions for CI/CD. Very simple but it works! Oh and a lot of bash scripts of course.

You can download Terraform from terraform.io and install it on your machine.

Claude also created the IAC for deploying the app on Hetzner, using Terraform as the configuration tool. I only had to provide my Hetzner API key for VPS resource provisioning and my Cloudflare API key for domain name DNS entry management. 🌐

Terraform Installed: Download and install Terraform from the website: https://www.terraform.io/

Be careful about linking to terraform docs for HCL, as it can be very easy to blur terraform's implementation of the behaviors from HCL itself

https://github.com/hashicorp/hcl/blob/v2.23.0/hclsyntax/spec... I believe is the actual language specification of heredocs

Similar to HCL which is way safer and clearer IMHO than all indent based craziness. Its lovely to see default values loaded thanks to some extra spaces. Brackets for the win!

https://github.com/hashicorp/hcl

This also reminds me of [HCL](https://github.com/hashicorp/hcl?tab=readme-ov-file#informat...)

Programming Model The first notable difference between Pulumi and Terraform is the programming language. Terraform uses a custom language called HashiCorp configuration language (HCL) to define infrastructure. In contrast, Pulumi offers more options, allowing you to choose from a list of popular programming languages.

Tenv utilizes go-version for semantic versioning and HCL parsing to extract version constraints from files like required_version in Terraform/OpenTofu or Terragrunt HCL files.

HCL is Hashicorp Configuration Language: https://github.com/hashicorp/hcl.

It's basically a DSL used by a bunch of Hashicorp products.

hcl is still MPLv2 https://github.com/hashicorp/hcl/blob/v2.23.0/LICENSE and my complaint is that the .go file has one import path but the compiler is going to secretly use a fork, versus updating the import path like a sane person. The only way anyone would know to check for why the complied code behaves differently is to know that trickery was possible

And that's not even getting into this horseshit: https://github.com/opentofu/hcl/blob/v2.20.1/go.mod#L1 which apparently allows one to declare a repos _import_ path to be different from the url used to fetch it

I have a similar complaint about how in the world anyone would know how "gopkg.in/yaml.v3" secretly resolved to

A Bake file can be written in HCL, YAML, or JSON. Docker recommends choosing HCL (HashiCorp Configuration Language) because it supports a more feature-complete Bake spec than the others. A valid Bake file should be called docker-bake followed by your chosen file extension.

In Kubernetes, we define deployments via YAML files. Whereas Nomad leverages HCL (HashiCorp Configuration Language).

Note that the Terragrunt configuration file uses the same HCL syntax as Terraform itself in terragrunt.hcl. Terragrunt also supports JSON-serialized HCL in a terragrunt.hcl.json file: where terragrunt.hcl is mentioned, you can always use terragrunt.hcl.json instead.