Add Support for rateLimitingOptions to google_compute_security_policy

[anovis]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

Add rate limiting options for google_compute_security_policy. This is the "rate limiting options" documented:

• https://cloud.google.com/compute/docs/reference/rest/beta/securityPolicies/addRule
• https://cloud.google.com/armor/docs/configure-security-policies#rate-limiting

New or Affected Resource(s)

• google_compute_security_policy

Potential Terraform Configuration

# Propose what you think the configuration to take advantage of this feature should look like.
# We may not use it verbatim, but it's helpful in understanding your intent.
resource "google_compute_security_policy" "policy" {
  provider = google-beta
  name = var.security_policy
  action = "throttle"

  rate_limit_options {
    exceed_action = "deny-429"
    enforce_on_key = "IP"
    rate_limit_threshold {
      count = 100
      interval_sec = 60
    }
  }
}

References

• b/198533060

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.