dynatrace_host_naming: Could not map JSON at 'rules[0].comparisonInfo.value'

[ajoga]

Describe the bug
When I try to apply my configuration [simplified for this ticket], it fails with the following error:

OpenTofu will perform the following actions:

  # dynatrace_host_naming.remove_fqdn will be created
  + resource "dynatrace_host_naming" "remove_fqdn" {
      + enabled = true
      + format  = "{Host:DetectedName}"
      + id      = (known after apply)
      + name    = "remove"

      + conditions {
          + condition {
              + os_arch {
                  + operator = "EQUALS"
                  + value    = "PARISC"
                }
            }
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  OpenTofu will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

dynatrace_host_naming.remove_fqdn: Creating...
╷
│ Error: Could not map JSON at 'rules[0].comparisonInfo.value' near line 1 column 165
│ 
│   with dynatrace_host_naming.remove_fqdn,
│   on environment_settings.tf line 1, in resource "dynatrace_host_naming" "remove_fqdn":
│    1: resource "dynatrace_host_naming" "remove_fqdn" {
│ 
╵

To Reproduce
Add this configuration to a terraform project that can already configure a Dynatrace environment:

resource "dynatrace_host_naming" "remove_fqdn" {
    enabled = true
    format = "{Host:DetectedName}"
    name = "remove"
    conditions {
        condition {
            os_arch {
                operator = "EQUALS"
                value = "PARISC"
            }
        }
    }
}

Run $ tofu apply

Expected behavior

The configuration is applied

Additional context

$ tofu version
OpenTofu v1.6.2
on linux_amd64
+ provider registry.opentofu.org/dynatrace-oss/dynatrace v1.56.2

Dynatrace managed version 1.284.143.20240314-155531

I followed this documentation to get key names and values: https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs/resources/host_naming#nestedblock--conditions--condition--application_type

I had the same issue with provider v1.54.2

[Dynatrace-Reinhard-Pilz]

Hi @ajoga , you've discovered a bug that must have existed for ages without anybody noticing. Thanks for reporting!
That bug will be fixed with the upcoming release of the provider.