You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attempting to leverage cloudposse/terraform-aws-budgets which pulls in this module. This module attempts to fetch hashicorp/template. The version 2.2.0 has been archived and recommends switching to templatefile. https://registry.terraform.io/providers/hashicorp/template/2.2.0 The problem is that template does not have an OSX m1/m2 release so it fails with:
│ Error: Incompatible provider version
│
│ Provider registry.terraform.io/hashicorp/template v2.2.0 does not have a package available for your current platform,
│ darwin_arm64.
│
│ Provider releases are separate from Terraform CLI releases, so not all providers are available for all platforms. Other
│ versions of this provider may have different platforms supported.
╵
Expected Behavior
The module works on OSX m1/m2
Steps to Reproduce
Steps to reproduce the behavior:
Attempt to use cloudposses/terraform-aws-budgets on OSX m1
Run terrform init
See error
Screenshots
N/A
Environment (please complete the following information):
Anything that will help us triage the bug will help. Here are some ideas:
OS: OSX
Version 12.6
Architecture arm
Additional Context
N/A
The text was updated successfully, but these errors were encountered:
Found a bug? Maybe our Slack Community can help.
Describe the Bug
Attempting to leverage cloudposse/terraform-aws-budgets which pulls in this module. This module attempts to fetch hashicorp/template. The version 2.2.0 has been archived and recommends switching to templatefile. https://registry.terraform.io/providers/hashicorp/template/2.2.0 The problem is that template does not have an OSX m1/m2 release so it fails with:
Expected Behavior
The module works on OSX m1/m2
Steps to Reproduce
Steps to reproduce the behavior:
Screenshots
N/A
Environment (please complete the following information):
Anything that will help us triage the bug will help. Here are some ideas:
Additional Context
N/A
The text was updated successfully, but these errors were encountered: