google_storage_transfer_job add support for path in gcp data sink

[mark-00]

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

We would like support for the path parameter in the gcp data sink as described in https://cloud.google.com/storage-transfer/docs/reference/rest/v1/TransferSpec#GcsData

We have a lot of source buckets which we want to aggregate in to one of destination buckets depending of the backup policy that is needed .

New or Affected Resource(s)

• google_storage_transfer_job

Potential Terraform Configuration

resource "google_storage_transfer_job" "s3-bucket-nightly-backup" {
  description = "Nightly backup of S3 bucket"
  project     = var.project
  transfer_spec {
    gcs_data_sink {
      bucket_name = google_storage_bucket.s3-backup-bucket.name
      path ="destinationpath/"
    }
  }
}

References

adding support for this parameter is a lot like adding support for the intevalPeriod #8578

Both can be handeld together

• #0000

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