│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
Relevant Error/Panic Output Snippet
│ "body":cty.List(cty.Object(map[string]cty.Type{"oversize_handling":cty.String})),
│ "cookies":cty.List(cty.Object(map[string]cty.Type{"match_pattern":cty.List(cty.Object(map[string]cty.Type{"all":cty.List(cty.EmptyObject),
│ "excluded_cookies":cty.List(cty.String), "included_cookies":cty.List(cty.String)})), "match_scope":cty.String, "oversize_handling":cty.String})),
│ "header_order":cty.List(cty.Object(map[string]cty.Type{"oversize_handling":cty.String})),
│ "headers":cty.List(cty.Object(map[string]cty.Type{"match_pattern":cty.List(cty.Object(map[string]cty.Type{"all":cty.List(cty.EmptyObject),
│ "excluded_headers":cty.List(cty.String), "included_headers":cty.List(cty.String)})), "match_scope":cty.String, "oversize_handling":cty.String})),
│ "ja3_fingerprint":cty.List(cty.Object(map[string]cty.Type{"fallback_behavior":cty.String})),
│ "json_body":cty.List(cty.Object(map[string]cty.Type{"invalid_fallback_behavior":cty.String,
│ "match_pattern":cty.List(cty.Object(map[string]cty.Type{"all":cty.List(cty.EmptyObject), "included_paths":cty.List(cty.String)})), "match_scope":cty.String,
│ "oversize_handling":cty.String})), "method":cty.List(cty.EmptyObject), "query_string":cty.List(cty.EmptyObject),
│ "single_header":cty.List(cty.Object(map[string]cty.Type{"name":cty.String})),
│ "single_query_argument":cty.List(cty.Object(map[string]cty.Type{"name":cty.String})), "uri_path":cty.List(cty.EmptyObject)})),
│ "text_transformation":cty.Set(cty.Object(map[string]cty.Type{"priority":cty.Number, "type":cty.String}))}))})}),
│ "visibility_config":cty.ListVal([]cty.Value{cty.ObjectVal(map[string]cty.Value{"cloudwatch_metrics_enabled":cty.True,
│ "metric_name":cty.StringVal("AWSManagedRulesUnixRuleSetMetric"), "sampled_requests_enabled":cty.True})})}) does not correlate with any element in actual.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Terraform Core Version
0.13+
AWS Provider Version
5.76.0
Affected Resource(s)
aws_wafv2_web_acl
Expected Behavior
association_config {
should be created,,..
Actual Behavior
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
terraform { backend "s3" {} required_providers { aws = { source = "hashicorp/aws" version = "= 5.76.0" } archive = { source = "hashicorp/archive" version = "= 2.2.0" } random = { source = "hashicorp/random" version = "= 3.1.0" } template = { source = "hashicorp/template" version = "= 2.2.0" } } required_version = ">= 0.13" }
Steps to Reproduce
add association block in the resource: aws_wafv2_web_acl, then plan and apply
:resource "aws_wafv2_web_acl" "example" { name = "large-request-body-example" scope = "REGIONAL"
default_action { allow {} }
association_config { request_body { api_gateway { default_size_inspection_limit = "KB_64" } } }
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None