terraform-provider-confluent: Error when provisioning schema with 1.32.0 version
Hello! I am getting the error during terraform plan:
[DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/confluentinc/confluent/1.32.0/linux_amd64/terraform-provider-confluent_1.32.0 args=[.terraform/providers/registry.terraform.io/confluentinc/confluent/1.32.0/linux_amd64/terraform-provider-confluent_1.32.0]
Error: failed to read provider configuration schema for registry.terraform.io/confluentinc/confluent: failed to instantiate provider "registry.terraform.io/confluentinc/confluent" to obtain schema: fork/exec .terraform/providers/registry.terraform.io/confluentinc/confluent/1.32.0/linux_amd64/terraform-provider-confluent_1.32.0: no such file or directory
terraform {
required_providers {
confluent = {
source = "confluentinc/confluent"
version = "1.32.0"
}
}
}
I’ve checked exactly the same code specifying versions 1.29.0, 1.30.0, 1.31.0 and it worked smoothly.
Does the latest version require a specific version of Terraform? I used 1.3.7.
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 1
- Comments: 15
Hi, I work with @msillence above. In our case, there is no cache to clear; we always run from a fresh Docker image in CI.
I believe this is caused by 1.32.0 being dynamically compiled, compared to earlier versions using static compilation. The plugin build works on my full-fat Ubuntu VM but not in the minimal
hashicorp/terraformcontainers we use for building.The following tested in the
docker.io/hashicorp/terraform:1.3.9container with my local plugin cache mounted. (The 1.26.0 lines are comparison - this is the next newest version I had installed.)It is not clear which further libraries would be required to make this version work. From our point of view, it would be very helpful to return to a static build, or something which works with the official Terraform container.
Sure - I use
podmanbut the following should also work fordocker. (I’m mounting my plugin cache here - depending on how Terraform is configured, you might want to mount something else.)To be able to run the
filetests, you would have to run within the container:I’ve run the same checks against plugin version 1.34.0 and this seems to execute happily in the container now. Many thanks!
👋 @petrkarytka @wahlfeld10x @neil-williamson thanks again for helping out with this issue!
As discussed, we returned to a static build in the latest release of TF provider (1.33.0).
Let me know if that helps!
Seeing this issue as well. We’re running 100s of TF jobs and use 10+ providers but this provider is the only one failing with this exact issue. Timeframe when the issue began is also the same as OP.
Thanks for the analysis @neil-williamson and others!
We’ll try to see whether we can deploy an easy fix otherwise we’ll roll back these changes in the next release of TF Provider.
@linouk23 This is not my case. I was trying to deploy from scratch when got the error.
Hi,
We’re experiencing the same issue and also using terraform 1.3.7
I tried upgrading to terraform 1.3.9 and it still fails
pinning the confluent module to <1.32 works