You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I was working with the module at the time, and I added an override rule to the managed_rule_group_statement_rules section. However, after executing the terraform plan, I received the following message:
Planning failed. Terraform encountered an error while generating this plan.
╷
│ Error: Unsupported block type
│
│ on .terraform/modules/waf/rules.tf line 568, in resource "aws_wafv2_web_acl""default":
│ 568: dynamic "challenge" {
│
│ Blocks of type"challenge" are not expected here.
╵
╷
│ Error: Unsupported block type
│
│ on .terraform/modules/waf/rules.tf line 568, in resource "aws_wafv2_web_acl""default":
│ 568: dynamic "challenge" {
│
│ Blocks of type"challenge" are not expected here.
╵
╷
│ Error: Unsupported block type
│
│ on .terraform/modules/waf/rules.tf line 568, in resource "aws_wafv2_web_acl""default":
│ 568: dynamic "challenge" {
│
│ Blocks of type"challenge" are not expected here.
╵
This behavior is observed with AWS provider version 5.9.0. It works if the provider version is updated to 5.13.0 or 5.17.0.
Expected Behavior
A plan containing all of the resources to be generated is displayed.
Steps to Reproduce
Create a terraform script with the rule and the override.
Describe the Bug
Hi,
I was working with the module at the time, and I added an override rule to the
managed_rule_group_statement_rules
section. However, after executing theterraform plan
, I received the following message:This behavior is observed with AWS provider version
5.9.0
. It works if the provider version is updated to5.13.0
or5.17.0
.Expected Behavior
A plan containing all of the resources to be generated is displayed.
Steps to Reproduce
terraform init
terraform plan
Screenshots
Terraform init screenshot:
Terraform plan error:
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: