Support for respecting filter order in aws_wafv2_web_acl_logging_configuration

[gdemarcsek]

Description

Adds an optional priority attribute to WAFv2 ACL logging configuration filters that can control the order in which the filters are supplied to the AWS API. This way it provides a non-breaking way to overcome the issue that the API actually represents the filters as an ordered list (array) and the order does affect the behaviour. At the same time, the current schema represents filters as a set.

Unfortunately, this is somewhat under-documented on AWS's side as well, but it is made clear on the console where it mentions:

If you add multiple filters, AWS WAF evaluates them starting from the top.

See also the linked issue.

Relations

Closes #32665

References

• https://docs.aws.amazon.com/waf/latest/APIReference/API_LoggingConfiguration.html
• https://docs.aws.amazon.com/waf/latest/APIReference/API_LoggingFilter.html
• https://docs.aws.amazon.com/waf/latest/developerguide/logging-management.html

Output from Acceptance Testing

% make testacc TESTS=TestAccWAFV2WebACLLoggingConfiguration_loggingFilter PKG=wafv2
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/wafv2/... -v -count 1 -parallel 20 -run='TestAccWAFV2WebACLLoggingConfiguration_loggingFilter'  -timeout 360m
=== RUN   TestAccWAFV2WebACLLoggingConfiguration_loggingFilter
=== PAUSE TestAccWAFV2WebACLLoggingConfiguration_loggingFilter
=== CONT  TestAccWAFV2WebACLLoggingConfiguration_loggingFilter


--- PASS: TestAccWAFV2WebACLLoggingConfiguration_loggingFilter (192.88s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/wafv2      200.140s
...

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
• Please see our prioritization guide for information on how we prioritize.
• 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.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.