Closed wenindoubt closed 1 year ago
Hello, checking in here is there a workaround for this issue ?
Hello, checking in here is there a workaround for this issue?
Thankfully, I haven't had to change my WAF since it got deployed. So technically, no workaround from me.
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.
Community Note
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
https://gist.github.com/wenindoubt/af67b4d3f041dae5d4c27b87e45abe6d
Panic Output
Expected Behavior
My
aws_wafv2_rule_group
was originally deployed with a capacity of 5. After changing the capacity to 2, I expectaws_wafv2_rule_group
to be updated in-place to 2.Actual Behavior
Steps to Reproduce
terraform apply
with the capacity as 5terraform apply
againImportant Factoids
References
0000