Can the M1 provider helper create providers for specific platforms on the .terraform.lock.hcl?

[giantryansaul]

Background:

Hi there, I recently got an M1 MacBook and decided to take on the task of getting our terraform configuration into a state that M1 machines could plan and apply with. That led me down the path of arriving at your tool, which solved some big headaches for me in working locally. I need some help understanding if I am going about this solution right.

For more background, my team still mostly has a lot of older Intel MacBooks but a couple of us are on new Apple silicone.

I was able to resolve 3 providers with your tool. The rest I resolved with small updates. I am using the m1-terraform-provider-helper lockfile upgrade command to resolve signature problems.

Question

Since we still mostly have developers on older Intel chipsets, I want to keep the lockfile intact for their platforms. I see that Terraform provides a way to create the lockfile for multiple platforms: terraform providers lock with multiple platforms specified.

Here is the command I want to run:
terraform providers lock -platform=darwin_amd64 -platform=linux_amd64 -platform=darwin_arm64 -platform=linux_arm64

When I run this with the darwin_arm64 platform I get the provider error:

│ Error: Could not retrieve providers for locking
│ 
│ Terraform failed to fetch the requested providers for darwin_arm64 in order to calculate their checksums: some providers could not be installed:
│ - registry.terraform.io/cyrilgdn/postgresql: provider registry.terraform.io/cyrilgdn/postgresql 1.11.2 is not available for darwin_arm64
│ - registry.terraform.io/datadog/datadog: provider registry.terraform.io/datadog/datadog 2.21.0 is not available for darwin_arm64
│ - registry.terraform.io/hashicorp/template: provider registry.terraform.io/hashicorp/template 2.2.0 is not available for darwin_arm64.

Question is: Am I going about this the wrong way? Since this command fails, my current plan is to use m1-terraform-provider-helper lockfile upgrade --output-path .terraform.lock.hcl.arm and have any M1 user copy the lock file over when they want to develop locally. Is there some step I'm missing here or is this the conventional way to go about M1 support?

[giantryansaul]

Its possible I'm way over-thinking this. I had a colleague get on a call with me, we tested the updated lock file, and it worked on their Intel-based MacBook. So I think the updated lockfile using the lockfile upgrade command is all that is needed to fix this.

[thekoma]

Confirmed that this solve the problem