@lra thank you for the workaround :)

The reason I've posted this bug report, is that:

• the change goes against CF Web UI that supports multiple integration types for the same notification policy.
• the change goes against CF API, which support multiple integration types - https://developers.cloudflare.com/api/operations/notification-policies-create-a-notification-policy
• there is no update of provider documentation regarding this change - https://registry.terraform.io/providers/cloudflare/cloudflare/4.21.0/docs/resources/notification_policy#example-usage

from terraform-provider-cloudflare.

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.

from terraform-provider-cloudflare.

Terraform debug log detected ✅

from terraform-provider-cloudflare.

The workaround is to have only 1 type of integration per notification policy.

Instead of:

resource "cloudflare_notification_policy" "pusher" {
  account_id = ""
  name       = "rate-limit"
  enabled    = true
  alert_type = "clickhouse_alert_fw_ent_anomaly"
  filters {
    services = ["ratelimit"]
    actions  = ["log"]
  }

  email_integration {
    id = "[email protected]"
  }

  webhooks_integration {
    id   = "someid"
    name = "Slack cloudflare alerts"
  }
}

Do:

resource "cloudflare_notification_policy" "pusher_email" {
  account_id = ""
  name       = "rate-limit"
  enabled    = true
  alert_type = "clickhouse_alert_fw_ent_anomaly"
  filters {
    services = ["ratelimit"]
    actions  = ["log"]
  }

  email_integration {
    id = "[email protected]"
  }
}

resource "cloudflare_notification_policy" "pusher_webhooks" {
  account_id = ""
  name       = "rate-limit"
  enabled    = true
  alert_type = "clickhouse_alert_fw_ent_anomaly"
  filters {
    services = ["ratelimit"]
    actions  = ["log"]
  }

  webhooks_integration {
    id   = "someid"
    name = "Slack cloudflare alerts"
  }
}

from terraform-provider-cloudflare.

thanks for the issue here @eLco.

@Cyb3r-Jak3 you added the ExactlyOneOf in #2976. was the change intending to prevent multiple blocks of config? it looks like the endpoints support it.

there is no update of provider documentation regarding this change - https://registry.terraform.io/providers/cloudflare/cloudflare/4.21.0/docs/resources/notification_policy#example-usage

we don't offer kitchen sink style examples so it's very likely not to appear here :) you should use the API and developer documentation to determine more complex examples.

from terraform-provider-cloudflare.

@Cyb3r-Jak3 you added the ExactlyOneOf in #2976. was the change intending to prevent multiple blocks of config? it looks like the endpoints support it.

Thought I read somewhere that only one could be referenced. Can't seem to find the docs for it now though.

from terraform-provider-cloudflare.

all good - if we can't find the reference, let's get that reverted for the next release.

from terraform-provider-cloudflare.