Incorrect Error on DNS Locations

[maxabaumgarten]

Confirmation

• This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team.
• 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

Terraform v1.10.4
on darwin_arm64

cloudflare provider: v4.50

Affected resource(s)

cloudflare_zero_trust_dns_location

Terraform configuration files

resource "cloudflare_zero_trust_dns_location" "test" {
  account_id     = 123456789
  name           = "test"
  client_default = true
  ecs_support    = true
  endpoints { #This is saying there's an error but its wrong. 
    doh {
      enabled = true
    }
    dot {
      enabled = true
    }
    ipv4 {
      enabled = false
    }
    ipv6 {
      enabled = false
    }
  }
}

Link to debug output

There's no actual error since the underlying API works

Panic output

No response

Expected output

I expect no errors to exist when using the endpoints block

Actual output

The endpoints block produces an "Unexpected block: Blocks of type "endpoints" are not expected here" issue on v4.50. The resource still deploys, but this should be fixed.

Steps to reproduce

use the endpoints block on cloudflare_zero_trust_dns_location

Additional factoids

There's no actual error since the underlying API works

References

No response

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[github-actions]

Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of TF_LOG=DEBUG output to be provided. The only parts that should be redacted are your user credentials in the X-Auth-Key, X-Auth-Email and Authorization HTTP headers. Details such as zone or account identifiers are not considered sensitive but can be redacted if you are very cautious. This log file provides additional context from Terraform, the provider and the Cloudflare API that helps in debugging issues. Without it, maintainers are very limited in what they can do and may hamper diagnosis efforts.

This issue has been marked with triage/needs-information and is unlikely to receive maintainer attention until the log file is provided making this a complete bug report.

[github-actions]

Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of TF_LOG=DEBUG output to be provided. The only parts that should be redacted are your user credentials in the X-Auth-Key, X-Auth-Email and Authorization HTTP headers. Details such as zone or account identifiers are not considered sensitive but can be redacted if you are very cautious. This log file provides additional context from Terraform, the provider and the Cloudflare API that helps in debugging issues. Without it, maintainers are very limited in what they can do and may hamper diagnosis efforts.

This issue has been marked with triage/needs-information and is unlikely to receive maintainer attention until the log file is provided making this a complete bug report.

[rexscaria]

Have you tried updating to latest v5? End points are supported from that version onwards.

[maxabaumgarten]

@rexscaria I have not because its not GA yet. We use 4.51 in prod.