cloudflare_custom_hostname inconsistent/not working

[ebuna]

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.0.11
on linux_amd64

• provider registry.terraform.io/cloudflare/cloudflare v4.17.0
• provider registry.terraform.io/hashicorp/azurerm v3.76.0
• provider registry.terraform.io/hashicorp/kubernetes v2.23.0
• provider registry.terraform.io/octopusdeploylabs/octopusdeploy v0.12.8

Affected resource(s)

• cloudflare_custom_hostname

Terraform configuration files

resource "cloudflare_custom_hostname" "example2" {

    zone_id              = "REDACTED"
    hostname             = "test16.ebuna.org"
    custom_origin_server = "prd-tnz-web.clubspark.pro"

    ssl {
        bundle_method         = "ubiquitous"
        certificate_authority = "google"
        method                = "txt"
        type                  = "dv"
        wildcard              = false
        
        settings {
            min_tls_version = "1.2"
            early_hints     = "on"
            http2           = "on"
            tls13           = "on"
        }
    }
}

Link to debug output

https://gist.github.com/ebuna/0cc856188a03490033572c30905e91b4

Panic output

N/A

Expected output

A successful plan/apply

Actual output

Error: Provider produced invalid plan
│
│ Provider "registry.terraform.io/cloudflare/cloudflare" planned an invalid value for cloudflare_custom_hostname.example2.wait_for_ssl_pending_validation: planned value cty.False for a non-computed
│ attribute.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Steps to reproduce

1. Use the example2 resource definition I submitted above
2. run terraform apply

Additional factoids

• Submitted this previously and it was closed (erroneously in my opinion)
• Adding the wait_for_ssl_pending_validation config to the example allows it to plan successfully, but running an apply will throw an error (after it applies), then any subsequent plan will also fail. Here is the gist for the same example2 resource but with the wait_for_ssl_pending_validation config set to false: gist
• Using the exact example provided in the documentation also causes a similar error

References

#2860

[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.