Cannot specify type = drop for cloudflare_email_routing_rule

[limejuny]

Current Terraform and Cloudflare provider version

Terraform v1.4.2
on linux_arm64

• provider registry.terraform.io/carlpett/sops v0.7.2
• provider registry.terraform.io/cloudflare/cloudflare v4.5.0

Your version of Terraform is out of date! The latest version
is 1.4.6. You can update by downloading from https://www.terraform.io/downloads.html

Description

Email rule actions should be one of forward, worker, drop. (https://developers.cloudflare.com/email-routing/setup/email-routing-addresses/#email-rule-actions)
But there was no drop in latest provider.
I think there should also be drop option.

Use cases

I want to catch all email to one destination, exclude specific address.
So I create new cloudflare_email_routing_rule resource, but there was no drop options.
I would also like to manage address (which will be dropped) with terraform.

Potential Terraform configuration

...
resource "cloudflare_email_routing_rule" "spam" {
  zone_id = cloudflare_zone.this.id
  name    = "spam"
  enabled = true

  matcher {
    type  = "literal"
    field = "to"
    value = "spam@custom.domain"
  }

  action {
    type  = "drop"
    value = []
  }
}

References

#1937
#1947

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

This functionality has been released in v4.20.0 of the Terraform Cloudflare Provider.

Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!