Allow request_payer argument for aws_s3_objects data source

[nnahaliel]

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

Description

Some S3 data sources/resources support setting request_payer (for example aws_s3_object_copy). I would like this argument to be available for aws_s3_objects as well.
My specific use case is fetching an object (who’s exact key I don't know in advance, but I can figure out from a list of existing objects) from a bucket owned by another account (where I only have permissions to get objects from that specific bucket). That bucket is a Requester Pays bucket.

New or Affected Resource(s)

• aws_s3_objects

Potential Terraform Configuration

data "aws_s3_objects" "matching_objects" {
  bucket        = var.remote_bucket
  prefix        = var.fetched_object_name_prefix
  request_payer = "requester"
}

References

• aws_s3_object_copy - request_payer
• aws_s3_objects

[github-actions]

This functionality has been released in v5.16.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. Thank you!

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.