tfenv VS ops

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

I ported a CLI tool I created from Ruby to Crystal, and it’s faster and it’s easier to install than the gem. The tool allows you to add simple automation with low cognitive overhead to any project without complex tools like Rake or Gradle.

If you have a simple project and would like to automate tasks without the complexity of something like rake or the pain of shell scripts, please give this gem (rubygems.org) a try (source is here (github.com)).

The docker-compose commands look a little cumbersome, though, and you’ll need something to manage secrets for you. Consider using ops to make them less verbose, and for helping new devs onboard.

Ejson files and ops.