cloudflare_zero_trust_dex_test: name attribute is both required and read-only

[Zapfmeister]

Confirmation

• This is a bug with an existing resource and is not a feature request or enhancement.
• I have searched the issue tracker and my issue isn't already found.
• I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version

Tested on both:

• cloudflare/cloudflare v5.18.0 (stable)
• cloudflare/cloudflare v5.19.0-beta.2

Using OpenTofu v1.11.5.

Affected resource(s)

cloudflare_zero_trust_dex_test

Terraform configuration files

resource "cloudflare_zero_trust_dex_test" "example" {
  account_id = "..."
  name       = "my-test"
  enabled    = true
  interval   = "30m"

  data = {
    host = "172.16.10.10"
    kind = "traceroute"
  }
}

Expected output

Resource created successfully with the given name.

Actual output

With name set:

Error: Invalid Configuration for Read-Only Attribute

  on main.tf line 3, in resource "cloudflare_zero_trust_dex_test" "example":
   3:   name       = "my-test"

Cannot set value for this attribute as the provider has marked it as read-only.

With name removed:

Error: Missing required argument

  on main.tf line 1, in resource "cloudflare_zero_trust_dex_test" "example":
   1: resource "cloudflare_zero_trust_dex_test" "example" {

The argument "name" is required, but no definition was found.

Steps to reproduce

1. Create a cloudflare_zero_trust_dex_test resource with name set → fails with "read-only attribute"
2. Remove name → fails with "required argument"

Additional factoids

The Cloudflare API documentation for Create DEX test lists name as a required field in the request body, which confirms the provider schema is incorrectly marking it as read-only.

The same issue exists for target_policies[].name — it's read-only in the provider but accepted by the API.

References

Tested with both v5.18.0 and v5.19.0-beta.2 — same behavior on both.

[KaydeeDee]

Thank you for submitting an issue! This issue has been flagged for an internal Cloudflare team to take a look. If this is urgently blocking your development or deployment, please open a support case so we can serve you faster.