Virtual Machines Data Source does not like custom field of type multiple selection

[jaket91-1]

I've run into an issue where the data type returned for a custom field in the netbox_virtual_machines data source does not match the expected type when the custom field is configured as Multiple selection, per below. All works when there is a custom field defined of type Text or no custom field defined, so it's definitely because of the Multiple selection type.

Terraform Version

❯ tofu --version
OpenTofu v1.6.0-dev
on darwin_amd64
+ provider registry.opentofu.org/e-breuninger/netbox v3.9.0

Netbox Version

v4.0.8

Affected Resource(s)

• data.netbox_virtual_machines

Terraform Configuration Files

❯ cat main.tf

variable "pve_host" {
  type    = string
  default = "https://pve.xxx.com:8006"
}

locals {
  cluster_name = replace(var.pve_host, "/https://|:.*/", "")
}

data "netbox_cluster" "query" {
  name = local.cluster_name
}

data "netbox_virtual_machines" "list" {
  filter {
    name  = "cluster_id"
    value = data.netbox_cluster.query.id
  }

Debug Output

❯ tofu plan
data.netbox_cluster.query: Reading...
data.netbox_cluster.query: Read complete after 1s [id=2]
data.netbox_virtual_machines.list: Reading...

Planning failed. OpenTofu encountered an error while generating this plan.

╷
│ Error: vms.0.custom_fields.ansible_roles: '' expected type 'string', got unconvertible type '[]interface {}', value: '[base]'
│
│   with data.netbox_virtual_machines.list,
│   on main.tf line 24, in data "netbox_virtual_machines" "list":
│   24: data "netbox_virtual_machines" "list" {
│
╵

Expected Behavior

Map of VM's returned.

Actual Behavior

Type failure because of the custom field definition in Netbox.

Steps to Reproduce

1. In Netbox, configure a VM custom field with the type Multiple selection
2. Add the netbox_virtual_machines data source to your TF config
3. terraform/tofu plan

[jaket91-1]

Just found #443. Will close this.