which terraformto find the the path to terraform (likely
/usr/local/bin/terraform). Whatever it is, jot down this installPath. You will need it in a bit.
Goto https://releases.hashicorp.com/terraform/ to see available versions. Choose the version you want based on the versions listed. You can click through on the hyperlinks to get the full base url for the download of interest.
uname -ain a terminal. For example I determined I should get the amd64 build, so I downloaded the
Download the correct file for the target terraform version, e.g.:
curl -O https://releases.hashicorp.com/terraform/1.0.7/terraform_1.0.7_linux_amd64.zip
Backup the old version using the installPath you determined earlier, e.g. assuming it's
# replace `.old` with a more useful suffix, like the old version number that's being archived. sudo mv /usr/local/bin/terraform /usr/local/bin/terraform.old
unzip the new download to the original installPath, noted earlier. e.g.:
sudo unzip terraform_1.0.7_linux_amd64.zip -d /usr/local/bin/
Check that you can invoke the new version!
terraform init again to reinitialise. If you run into problems, don't forget to make edits to your tf files according to the upgrade guides and your chosen upgrade path (eg, some syntax has likely changed). To force upgrade the state / automate migration of state:
terraform init -migrate-state
In my case,
-migrate-state with my s3+dynamodb backend didn't work! kept complaining about locks. tried with
init -reconfigure and still no joy. Nuked the dynamodb table entries. There was still an issue so I went into the S3 bucket and just nuked everything, came back and nuked the .terraform folder as well, then init was happy.
Imagine if this had been a real prod environment!
Ran into needing these steps because:
--rm <tf-command-here>each time I wanted to use that version of tf, and I didn't want to get sidetracked with tfenv / tfswitch...