[Enhancement]: aws_s3_bucket_lifecycle_configuration filter definition should be normalized into an obect or map

[vampirechicken]

Description

Update the AWS provider allow us to pass in the filter values as a map or object with a nested map/object of tags, and have the provider determine what to do with it. The status quo makes this logic a nightmare as we try to write a module for these resources:

• differing syntax between one tag vs multiple tags
• and {} block that is only needed sometime, and feels like it could be inferred by the HCL parser.

Affected Resource(s) and/or Data Source(s)

• aws_s3_bucket_lifecycle_configuration

Potential Terraform Configuration

filters = {
     prefix = "myoptionalprefix"
     tags   = {
       key1 = value1
       # maybe more tags
     }
     # other filter params
  }

References

No response

Would you like to implement a fix?

None

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this 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.

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.