hcledit VS tfenv

To automate the process of injecting CI/CD runtime information into our Terraform code, we'll introduce the tool hcledit. With hcledit and some other manipulation, we can insert data into the Terraform code using regex/grep to find the correct place to add it.

I would suggest a CI step that reads the .terraform-version file and then uses hcledit to update that block in the code.

If you want to actually transform the HCL, use hcledit: https://github.com/minamijoyo/hcledit

The hclwrite library is pretty low-level and not convenient to use for quick scripting, but hcledit is a higher-level wrapper around it which works nicely for relatively straightforward situations.

You'll need the correct version of Terraform (the version of Terraform used for apply can be found in terraform_version at the beginning of the .tfstate file), to switch between versions I recommend tfenv.

For almost four years I'd been using a Macbook as my main work machine. One quality of life tool I'd gotten used to was tfenv, a lovely little tool for managing terraform versions & quickly switching between them.

For example terraform state files often have non backwards compatible changes. You should consider using something like tfenv so everyone on your team has identical versions of terraform.

I'm using the tool tfenv to manage Terraform versions. Other tools can do that. You can use asdf, too. I saw that asdf can do more than manage Terraform versions.

Documentacion TFENV

git clone https://github.com/tfutils/tfenv.git ~/.tfenv export PATH="$HOME/.tfenv/bin:$PATH" # install to appropriate shell startup file, e.g. $HOME/.bashrc echo 'export PATH="$HOME/.tfenv/bin:$PATH"' >> ~/.profile