Cloudflare Notification Policy - magic_tunnel_health_check_event not working.

[miteshchauhan]

Confirmation

• [X] 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.
• [X] I have searched the issue tracker and my issue isn't already found.
• [X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version

Terraform v1.7.5 on darwin_arm64

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

Affected resource(s)

cloudflare_notification_policy alert_type = "magic_tunnel_health_check_event"

Terraform configuration files

resource "cloudflare_notification_policy" "magic-tunnel-health" {
  account_id = local.stepstone_cloudflare_account_id
  name       = "TF - Magic Tunnel Health Check Alert"
  alert_type = "magic_tunnel_health_check_event"
  enabled    = true
  email_integration {
    id = "yyy"
  }
  email_integration {
    id = "xxx"
  }
  filters {
    tunnel_id = ["zzz"]
    slo = ["90"]
  }
}

Link to debug output

N/A

Panic output

No response

Expected output

resource should be applied successfully

Actual output

│ Error: error creating policy TF - Magic Tunnel Health Check Alert: Invalid object selections (17003) │ │ with cloudflare_notification_policy.magic-tunnel-health, │ on magic-tunnel-health.tf line 1, in resource "cloudflare_notification_policy" "magic-tunnel-health": │ 1: resource "cloudflare_notification_policy" "magic-tunnel-health" { │

Steps to reproduce

1. try to deploy any magic-tunnel health check will give you the error. it's not clear what the requirements are for this type of check (was hoping to have it managed within TF then we could update the config based on changes made on the Dash portal)
2. try to import any magic-tunnel health check will give a different error

Additional factoids

We also face issues when importing pre-existing magic-tunnel-health checks into an empty resource. We get the following error message:

Error: failed to set filters: Invalid address to set: []string{"filters", "0", "tunnel_name"}

Ticket also raised within CF No#3221552

References

No response

[github-actions[bot]]

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

[Nmishin]

I see that magic_tunnel_health_check_event was added in this PR https://github.com/cloudflare/terraform-provider-cloudflare/pull/2937 by @jasoncabot and released as a part of 4.20.0 version

Unfortunately I don't have that type of alerts in my CF account, and I can't test/fix it. @jasoncabot Jason, maybe you can?

[jeffsani]

Posting my debug log for the same issue. We are missing something in the provider that is required by the Tunnel Health Check API -

Error: Unsupported argument on cf_aws_mwan_tunnels_and_routes.tf line 72, in resource "cloudflare_notification_policy" "AWS-VPN-1-Notification": tunnel_name = ["AWS-VPN-1"] An argument named "tunnel_name" is not expected here.

run-y3QFHPNd7eTSgjmt-plan-log.txt

[github-actions[bot]]

Marking this issue as stale due to 30 days of inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 7 days it will automatically be closed. Maintainers can also remove the lifecycle/stale label. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[github-actions[bot]]

This issue was closed because it has been stalled for 7 days with no activity.