This message was deleted Rancher Users #terraform-provider-rancher2

Join Slack

This message was deleted.

# terraform-provider-rancher2

adamant-kite-43734

05/04/2023, 10:05 AM

This message was deleted.

sparse-fireman-14239

05/04/2023, 10:07 AM

https://developer.hashicorp.com/terraform/tutorials/configuration-language/provider-versioning

quiet-author-51481

05/04/2023, 10:12 AM

Thanks, I have a version.tf with

Copy code

terraform {
  required_version = ">= 1.3"
}

which generates tf.lock.hcl :

Copy code

provider "<http://registry.terraform.io/rancher/rancher2|registry.terraform.io/rancher/rancher2>" {
  version     = "3.0.0"
  constraints = ">= 1.24.1"

and I can see the

3.0.0

version being used from tf logs:

Copy code

DEBUG] provider.terraform-provider-rancher2_v3.0.0: 2023/05/04 13:00:21 [INFO] Creating Cluster XXX

So, I have to specify the required_version in version.tf a bit differently probably

quiet-author-51481

05/04/2023, 10:14 AM

But I am not understanding how this mapping matrix is working, is there a table for that? in other words, how would I find out the needed

required_version

for specific rancher provider version

sparse-fireman-14239

05/04/2023, 10:16 AM

It's a provider version, not K8s version

quiet-author-51481

05/04/2023, 10:18 AM

yes, and both are available: v3.0.0 & v1.24.2

quiet-author-51481

05/04/2023, 10:19 AM

though I am not sure why it was previously following the k8s version for provider and then stopped it after v1.25.0 release (next release versioning is v2.0.0-rc1)

sparse-fireman-14239

05/04/2023, 10:20 AM

It's probably in the docs/release notes

quiet-author-51481

05/04/2023, 10:36 AM

Not really, but for anyone who could stumble upon this in the future, you can tune the

required_version

as following:

Copy code

terraform {
  required_version = "<= 1.24.3"
}

and it will install the provider version v1.24.2

15 Views

Open in Slack

Previous Next