"Please activate first" when installing template provider

[Mark Walker]

I'm working with a project that uses the deprecated template provider somewhere which doesn't work on my M2.

Expected Behavior

Install the template provider using m1-terraform-provider-helper install hashicorp/template -v v2.2.0

Actual Behavior

❯ m1-terraform-provider-helper install hashicorp/template -v v2.2.0
Please activate first

Steps to Reproduce (including precondition)

1. Remove any existing Terraform binary (/usr/bin/terraform and/or /usr/local/bin/terraform)

2. Install m1-terraform-provider-helper 2.5k

   • brew install kreuzwerker/taps/m1-terraform-provider-helper

3. Install Terraform

   • brew tap hashicorp/tap
   • brew install hashicorp/tap/terraform

4. Install the hashicorp/template version v2.2.0

   • m1-terraform-provider-helper install hashicorp/template -v v2.2.0

Your Environment

• OS: 14.3.1 (23D60)
• m1-terraform-provider-helper version: 0.9.0

[Mark Walker]

Oh wow. That was easier than I expected.

m1-terraform-provider-helper activate

❯ tf init

Initializing the backend...
Initializing modules...

Initializing provider plugins...
- Finding latest version of hashicorp/template...
- Reusing previous version of hashicorp/random from the dependency lock file
- Reusing previous version of carlpett/sops from the dependency lock file
- Reusing previous version of alxrem/jsonnet from the dependency lock file
- Reusing previous version of hashicorp/google from the dependency lock file
- Reusing previous version of petoju/mysql from the dependency lock file
- Using previously-installed hashicorp/google v5.10.0
- Using previously-installed petoju/mysql v3.0.30
- Installing hashicorp/template v2.2.0...
- Installed hashicorp/template v2.2.0 (unauthenticated)
- Using previously-installed hashicorp/random v3.6.0
- Using previously-installed carlpett/sops v0.7.2
- Using previously-installed alxrem/jsonnet v2.2.0

Terraform has made some changes to the provider dependency selections recorded
in the .terraform.lock.hcl file. Review those changes and commit them to your
version control system if they represent changes you intended to make.

╷
│ Warning: Incomplete lock file information for providers
│ 
│ Due to your customized provider installation methods, Terraform was forced to calculate lock file checksums locally for the following providers:
│   - hashicorp/template
│ 
│ The current .terraform.lock.hcl file only includes checksums for darwin_arm64, so Terraform running on another platform will fail to install these providers.
│ 
│ To calculate additional checksums for another platform, run:
│   terraform providers lock -platform=linux_amd64
│ (where linux_amd64 is the platform to generate)
╵

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.