`cloudflare_tunnel_route` is not removed when contains `virtual_network_id`

[vavsab]

Confirmation

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

Terraform and Cloudflare provider version

Cloudflare plugin: v3.20.0

Affected resource(s)

cloudflare_tunnel_route

Terraform configuration files

I'm using Pulumi wrapper. But the idea is

resource "cloudflare_argo_tunnel" "tunnel" {
	account_id = "accid"
	name       = "example"
	secret     = "AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg="
}

resource "cloudflare_tunnel_route" "route" {
    account_id = "accid"
    tunnel_id = cloudflare_argo_tunnel.tunnel.id
    network = "10.1.1.0/24"
    virtual_network_id = "vnetidhere"
    comment = "Test"
}

Debug output

Panic output

No response

Expected output

When tunnel route is removed via terraform then tunnel route is removed from Cloudflare.

Actual output

Result is displayed as successful but tunnel route is still present in Cloudflare after removal via terraform

Steps to reproduce

1. Create tunnel route with vnet with TF
2. Remove tunnel route with TF
3. Check that tunnel route is still present.

Additional factoids

No response

References

No response

[github-actions[bot]]

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.

[vavsab]

Did not check but should be fixed now.