Closed lirany1 closed 10 months ago
I was running into the same problem with vmware/vra
and vmware/nsxt
. I'm running in a github action on a local runner and the hashicorp/setup-terraform
step was using update to latest. If I pinned this at v1.5.7, I could get a successful terraform init
to run.
This seems to be something introduced in a later terraform version...likely v1.6.0.
It seems a change was introduced in terraform v1.6.0, see https://github.com/hashicorp/terraform/issues/33984. I'm not sure at this point if we need to re-key our provider binaries or if terraform will publish a (temporary) fix. I'll keep an eye on that issue. In the meantime, as @kglueck stated, pin the terraform version to v1.5.7.
I just cut a new release v0.8.2 signed with an un-expired key. We'll verify it once the release is refreshed at the Terraform Registry.
Thanks but now getting this error:
terraform init
Initializing the backend...
Initializing provider plugins...
- Finding vmware/vra versions matching "0.8.2"...
╷
│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider vmware/vra: no available releases match the given constraints 0.8.2
╵
The new version is not yet published at the Terraform Registry. Additionally, there seems to be a problem with the way the registry uses the signing key. I'd recommend sticking with terraform v1.5.7 or switching to v1.6.1. when released.
vRA Version
8.11.2
Terraform Version
1.6.0
vRA Terraform Provider Version
0.8.1
Expected Behavior
should deploy vm
Actual Behavior