tfenv VS driftctl

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

‍Driftctl is an open-source Terraform drift detection tool that tracks and warns about infrastructure drift. Driftctl scans your infrastructure, compares it with your IaC configurations (like Terraform), and reports discrepancies.

their decoder https://github.com/snyk/driftctl/tree/main/pkg/iac/terraform/state

Drift detection is a pain for us as it is today, we are planning on adding another tool to the stack to solve this problem, like snyk/driftctl

driftctl. That is all.

I use driftctl running as a scheduled task as a GitHub action to monitor for state changes not matching config.

https://github.com/snyk/driftctl is for comparing approved resources by looking at your IAC state to what is actually out there in your clouds.

A quick search engine browse returns the following