Feature Request: WAFv2 IP Set Resource

[bflad]

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

Description

In November 2019, AWS released a new version of the WAF API, WAFv2, which offers improved functionality over the previous WAF API ("WAF Classic") such as Managed Rules and WAF Capacity Units. This new API requires separate Terraform resource implementations from the previous resource implementations.

New or Affected Resource(s)

• aws_wafv2_ip_set

Potential Terraform Configuration

resource "aws_wafv2_ip_set" "example" {
  addresses          = [""]
  description        = ""
  ip_address_version = ""
  name               = ""
  scope              = ""
  tags               = {}
}

References

• Requires: service/wafv2: Initial service client and tagging implementation #11172
• API Reference: https://docs.aws.amazon.com/waf/latest/APIReference/API_Operations_AWS_WAFV2.html
• SDK Reference: https://docs.aws.amazon.com/sdk-for-go/api/service/wafv2/

[tsabbay]

This entire wafv2 is not baked!

[anGie44]

The fix for this has been merged and will release with version 2.63.0 of the Terraform AWS Provider, expected in this week's release.

[ghost]

This has been released in version 2.63.0 of the Terraform AWS 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 for triage. Thanks!

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!