This message was deleted.
# harvester
a
This message was deleted.
b
Hi @cuddly-restaurant-47972, > Can I get an update on the Terraform Harvester Provider? Currently the latest version is 0.6.4, if you want to built on your own version, you can check https://github.com/harvester/terraform-provider-harvester/pull/93, I've done this once before for testing. (see the Test Plan in pr description) > Is it being actively maintained? Yes, terraform provider harvester is the official way to deploy VM to harvester, and is under maintained. > Is there a way to be able to do Pull Requests or submit bug reports? Please submit bug issue to harvester repo if you encounter any problems. and feel free to raise PR. Normally we raise an issue first and then file PR. > I know the provider is not working with the latest version of harvester because there is a missing label and I don't see a BR or PR for it. Could you explain more ? What do you mean not working ? And what label is missing ? Thank you.
c
It has been more than a month since I tried the deployment on our version of Harvester, but pretty sure this is the label needed: labels: harvesterhci.io/vmName:
I tried submitting a bug at the time but I was not able to create an issue.
Actually this is why I could not create an issue. Maybe I am just missing something obvious:
I mean I just manually went to the issues page and they are there, but not sure why you don't have the tab up there by default.
b
I tried submitting a bug at the time but I was not able to create an issue.
Yeah, we disable the issue tab in the terraform-provider-harvester github repo, if you encounter any issues (no matter which part, terraform, storage, network, helm chart .etc.), please raise issue to harvester github repo https://github.com/harvester/harvester. We are doing this since it's more easily for us to manage the whole project.
1
c
And I feel like I was completely wrong about the label issue and not sure how I deduced that piece. What is the proper way to use a cloudinit enabled image with the Terraform provider? Right now in my disk specification I am using a image id that was previously gleaned from a data.harvester_image reference. But my PVC never mounts. Should I be using container_image_name in my disk {} block instead of the image reference in the disk {} block?
b
c
The resource "harvester_image" "ubuntu"? name = "ubuntu"? or display_name = "ubuntu"? makes the example a little confusing to be fair. But I am using a data instead of a resource since the image has already been downloaded onto my cluster. This is my data.harvester_image. Should I put IMG in there or put the var.image_name in there? I was just referencing the .id value returned from this data.harvester_image but it is not working for some reason. data "harvester_image" "img" { display_name = var.img_display_name namespace = var.img_namespace }