free download Directory List & Print 4.29

When I run terraform init for the same plugin version in another directory, it is accessed from the cache, and only h1 hash is written into the lock file.If I will use this lock file on a different machine everything works as expected.

When I run terraform init that resolved to a plugin version that is not in the cache, Terraform actually does it's job: it downloads the plugin, populates the lock file with all zhs and a single h1.

The only problem is that, somehow, Terraform always does a little different thing for me: Sounds great, actually (or one can assume we can remember h1s directly, but it's not my expertise). Documentation states that even though h1s only for current architectures are populated, since zhs are always present they are enough to check either plugin for a new architecture already matches known hashes, so that Terraform can append new h1 hash on a first download.

Since we use Terraform on several machines, and some developers are using different architectures (I'm using Linux Amd64, my colleague is using Darwin Amd64, more architectures might come with M1), I expect lock files to support being used on several architectures. Also, at some point in time I started using lock files instead of relying on using version = '= x.y' to always reuse the same version.

So, since I am using several stacks of Terraform configuration quite regularly and their plugins in use are mostly the same, I didn't want providers to be downloaded for each one, so I enabled plugin cache directory (see below).

Free download Directory List & Print 4.29