Closed simonlock closed 7 months ago
This problem occurs when the version of Terraform Provider is older. Try changing the version specification to version = "~> 3.0"
Thank you so much for your quick reply and suggestion. However, changing the version specification to version = "~> 3.0" didn't solve this issue. Running "terraform init" followed by "terraform validate" produces the same errors.
terraform --version
Terraform v1.7.2
on linux_arm64
+ provider registry.terraform.io/hashicorp/azurerm v3.0.2
+ provider registry.terraform.io/hashicorp/random v3.1.0
Thanks for your help on this. Found these links:
https://github.com/hashicorp/terraform-provider-azurerm/issues/21006 https://github.com/hashicorp/terraform-provider-azurerm/blob/v3.49.0/CHANGELOG.md
setting: version = "~> 3.49.0"
terraform init -upgrade
Fixed this issue.
terraform --version
Terraform v1.7.2
on linux_arm64
+ provider registry.terraform.io/hashicorp/azurerm v3.49.0
+ provider registry.terraform.io/hashicorp/random v3.1.3
Hi shibayan
The terraform module seems to no longer work and fails the terraform validation, but the Arm template works great.
Issuing the "terraform validate" produces:
This is whilst explicitly defining the required 5 variables e.g.
and whilst using the azurerm provider:
I might be doing something wrong.
Btw does the terraform module require a pre-existing key vault to exist, unlike the Arm template?