Add google_storage_transfer_job support for AWS RoleArn for temporary credentials

[lanre-OG]

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 "me too" comments, 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. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

Google Cloud storage transfer job module does not support using Role_Arn for AWSS3Data. The Amazon Resource Name (ARN) of the role to support temporary credentials via AssumeRoleWithWebIdentity. Transfer Service fetches temporary credentials for the session using a AssumeRoleWithWebIdentity call for the provided role using the GoogleServiceAccount for this project.

New or Affected Resource(s)

• google_storage_transfer_job

Potential Terraform Configuration

# Propose what you think the configuration to take advantage of this feature should look like.
# We may not use it verbatim, but it's helpful in understanding your intent.

    aws_s3_data_source {
      bucket_name = var.aws_s3_bucket
      roleArn = var.role_arn
    }

References

• GCP TransferSpec
• GCP storage_transfer_job
• GCP Federated Identity

[upodroid]

This is duplicate of #10844

[shuyama1]

Thanks @upodroid! Looks like it is a duplicate of #10844, and I am closing this issue. @Jseph Thank you for your contribution and would you mind link your PR against #10844. Simply modify your PR description would work. Thanks a lot!

[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.