T12:14:37.153-0400 provider: starting plugin: path=.terraform/providers//hashicorp/azurerm/3.7.0/windows_amd64/terraform-provider-azurerm_v3.7.0_x5.exe args= T12:14:37.144-0400 provider: configuring client automatic mTLS T12:14:37.144-0400 ntextPlugins: Initializing provider “ Terraform Registry” to read its schema │ needs to be recompiled to support the latest protocol… │ This usually means that the plugin is either invalid or simply │ “ Terraform Registry” to obtain schema: Unrecognized remote plugin message: │ provider Terraform Registry failed to instantiate provider │ Error while loading schemas for plugin components: Failed to obtain provider schema: Could not load the schema for I’m running out of steam looking at wireshark, fiddler, tcpview, procmon, eventviewer, and everything else trying to figure out this issue. We uninstalled crowdstrike altogether and that did not resolve the issue. We saw a very similar sounding issue in relation to machines with trend AV, we do not have that but do have crowdstrike. We’ve worked with our firewall/zscaler team to rule out any firewall blocks (shouldn’t be the case as we can query provider registry, and Terraform-Provider-Azurerm Versions | HashiCorp Releases). terraform directory and lock file and rerun init, we’ve tried different versions of the azurerm plugin (2.9.9, 3.7.0), different versions of terraform (1.1.5, 1.1.7, 1.2.0). We’ve tried on multiple workstations, we’ve deleted the. When we copy repo to a workstation for local testing (lenovo laptop running win10, not an apple using M1 chip), terraform init works great (and is able to download providers without issue) however terraform plan, validate, or apply always fail. We have an ADO repo setup to run terraform in pipeline, it works properly.
0 Comments
Leave a Reply. |