Resource "cloudflare_zone" jump_start flag not working

[lensbart]

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.9.7
on darwin_arm64

• provider registry.terraform.io/cloudflare/cloudflare v4.43.0

Affected resource(s)

cloudflare_zone

Terraform configuration files

terraform {
  required_providers {
    cloudflare = {
      source  = "cloudflare/cloudflare"
      version = "~> 4"
    }
  }
}

variable "account_id" {
  default = "my-account-id"
}

resource "cloudflare_record" "www" {
  content = "1.2.3.4"
  name    = "www"
  proxied = true
  type    = "A"
  zone_id = cloudflare_zone.mydomain.id
}

resource "cloudflare_zone" "mydomain" {
  account_id = var.account_id
  jump_start = false
  plan       = "free"
  zone       = "mydomain.com"
}

Link to debug output

https://gist.github.com/lensbart/55dc9fef8e2b0223a1654aa6076225f9

Panic output

No response

Expected output

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

Actual output

Plan: 2 to add, 0 to change, 0 to destroy.
cloudflare_zone.mydomain: Creating...
cloudflare_zone.mydomain: Still creating... [10s elapsed]
cloudflare_zone.mydomain: Creation complete after 10s [id=some-id]
cloudflare_record.www: Creating...
cloudflare_record.www: Still creating... [10s elapsed]
cloudflare_record.www: Still creating... [20s elapsed]
cloudflare_record.www: Still creating... [30s elapsed]
╷
│ Error: expected DNS record to not already be present but already exists
│ 
│   with cloudflare_record.www,
│   on cloudflare.tf line 14, in resource "cloudflare_record" "www":
│   14: resource "cloudflare_record" "www" {
│ 
╵

Steps to reproduce

• Have a domain with www DNS record
• Create a Cloudflare zone for this domain via Terraform
• Add a www record to this zone with Terraform as described above

Additional factoids

No response

References

Same issue as #826, which (judging by the comments) seems to have been closed erroneously

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

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