Provide a way to configure platforms for Dependency lock file generation

[swanandvk]

Current Terraform Version

0.14

Use-cases

After performing terraform init .terraform.lock.hcl is generated
which by default is generated for the platform on which user is running terraform init
and with the help of following commands file is updated for other platforms as well

terraform providers lock \
  -platform=linux_arm64 \
  -platform=linux_amd64 \
  -platform=darwin_amd64 \
  -platform=windows_amd64

Attempted Solutions

Proposal

• providing a way to configure default platforms for generating dependency lock will make it easy for generating it for predefined platforms by just running terraform init instead of manually fixing the file later

• the possible configure option I can think of is .terraformrc

• example

provider_installation {

  platforms =[
  linux_arm64, 
  linux_amd64, 
  darwin_amd64, 
  windows_amd64
  ]
}

References

[acdha]

Related issue: #27811 — this problem is massively amplified by terraform providers lock not using the cache.

One alternate proposal: extend the lock file syntax to include the platforms list so the logic could simply be that it will always download and lock the same platforms which were already present in the file. I'm not sure it'd be worth the compatibility hit of changing something like this:

provider "registry.terraform.io/hashicorp/aws" {
  version     = "3.64.2"
  constraints = ">= 3.28.0, >= 3.63.0, ~> 3.63"
  hashes = [
      …  
  ]
}

to

provider "registry.terraform.io/hashicorp/aws" {
  version     = "3.64.2"
  constraints = ">= 3.28.0, >= 3.63.0, ~> 3.63"
  hashes = {
    "linux_amd64": […],
    …  
  }
}

but it seems like this would be an easy way to avoid that while still accomplishing the same goal:

provider "registry.terraform.io/hashicorp/aws" {
  version     = "3.64.2"
  constraints = ">= 3.28.0, >= 3.63.0, ~> 3.63"
  platforms = [
    "linux_amd64",
    "linux_arm64",
    "darwin_amd64",
    "darwin_arm64"
  ]
  hashes = [
      …  
  ]
}