aws_wafv2_web_acl_logging_configuration: terraform plan says "Not supported by WAFv2 API" with single_header

[kamatama41]

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 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
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v0.13.4

• provider registry.terraform.io/hashicorp/aws v3.33.0

Affected Resource(s)

• aws_wafv2_web_acl_logging_configuration

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

resource "aws_wafv2_web_acl_logging_configuration" "waf_acl_logging" {
  log_destination_configs = [aws_kinesis_firehose_delivery_stream.waf_logs_stream.arn]
  resource_arn            = aws_wafv2_web_acl.waf_acl.arn
  redacted_fields {
    single_header {
      name = "cookie"
    }
  }
}

Debug Output

Panic Output

Expected Behavior

Warning message should not be shown.

Actual Behavior

Warning message is shown.

Steps to Reproduce

1. terraform plan

Important Factoids

References

• 14248

The deprecation warning seems to be caused by the pull request, but I think single_header should not be deprecated because it's still valid option.

[ghost]

This has been released in version 3.34.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!