Unable to create MX records with "." as value since v.3.18.0

[nozaq]

Confirmation

• My issue isn't already found on the issue tracker.
• I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version

• Terraform: v1.3.5 (the latest)
• Cloudflare provider: v3.28.0 (the latest)

Terraform v1.3.5
on linux_amd64
+ provider registry.terraform.io/cloudflare/cloudflare v3.28.0

Affected resource(s)

• cloudflare_record

Terraform configuration files

resource "cloudflare_record" "mx" {
  zone_id  = var.zone_id
  type     = "MX"
  name     = "example"
  value    = "."
  priority = 0
}

Link to debug output

https://github.com/nozaq/cloudflare-null-mx/blob/main/debug_log.txt

Panic output

No response

Expected output

cloudflare_record resource will be successfully created.

Actual output

terraform apply fails with the following output.

cloudflare_record.mx: Creating...
╷
│ Error: either 'value' (present: false) or 'data' (present: false) must be provided
│
│   with cloudflare_record.mx,
│   on main.tf line 10, in resource "cloudflare_record" "mx":
│   10: resource "cloudflare_record" "mx" {
│
╵

Steps to reproduce

1. Run terraform init
2. Run terraform apply -auto-approve

Additional factoids

This issue seems happening since v3.18.0.

I've confirmed that terraform apply succeeded without any error with the Cloudflare provider v3.17.0, but failed with v3.18.0

The example project is at https://github.com/nozaq/cloudflare-null-mx.

References

The same issue was fixed last year in v2.19.1(#984). Few people mentioned that the similar issue happening again this year, but unfortunately nobody responded to these reports yet.

[github-actions]

Terraform debug log detected ✅

[github-actions]

This functionality has been released in v3.29.0 of the Terraform Cloudflare Provider.

Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!