Closed kaykhan closed 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
Just this morning we see this same issue when adding a rule to a aws_wafv2_web_acl
. Terraform v1.3.7 with AWS provider v4.49.0 and v4.50.0
Just this morning we see this same issue when adding a rule to a
aws_wafv2_web_acl
. Terraform v1.3.7 with AWS provider v4.49.0 and v4.50.0
Let me know if you find a workaround or version that works.
Experiencing the same issue. Some notes:
aws_wafv2_web_acl
with AWS-AWSManagedRulesATPRuleSet
succeedsaws_wafv2_web_acl
object with AWS-AWSManagedRulesATPRuleSet
attached also leads to panicA workaround at this point would involve avoiding changing the resource but to destroy the resource, recreate the resource, and then making sure any resource that references the waf also gets updated.
I was able to work around the issue by removing all existing rule
s from the aws_wafv2_web_acl
, running terraform apply
, then adding all the rules that I want to the aws_wafv2_web_acl
and applying again. So it works to remove all rules or add all rules to a WAF with no rules - but not add a new rule to a WAF with existing rules.
I was able to work around the issue by removing all existing
rule
s from theaws_wafv2_web_acl
, runningterraform apply
, then adding all the rules that I want to theaws_wafv2_web_acl
and applying again. So it works to remove all rules or add all rules to a WAF with no rules - but not add a new rule to a WAF with existing rules.
thanks, I think it would be inconvenient for us if we had to remove all rules and readd all rules ( including the new one) each time, if i understand this work around correctly.
In my environment,
override_action {
count {}
}
then the apply will succeed.
If I change it to none {}
, it panics.
Seeing the same issue.
In the versions.tf, anything above 4.30.0 causes WAF deployment issues with AWSManagedRulesKnownBadInputsRuleSet.
This functionality has been released in v4.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. Thank you!
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.
Terraform Core Version
1.3.6
AWS Provider Version
4.50.0
Affected Resource(s)
aws_wafv2_web_acl
Expected Behavior
Expeect the rule group "AWS-AWSManagedRulesATPRuleSet" to be added to my existing WAF.
Actual Behavior
Error
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
terraform apply -var-file="prod.tfvars"
Debug Output
No response
Panic Output
https://gist.github.com/kaykhan/4d7961c964fbce400aa476f1c3bfdae1
Important Factoids
No response
References
No response
Would you like to implement a fix?
None