You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
mark-00
changed the title
google_storage_transfer_job add support for path
google_storage_transfer_job add support for path in gcp data sink
Mar 16, 2021
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.
Community Note
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)
Potential Terraform Configuration
References
adding support for this parameter is a lot like adding support for the intevalPeriod #8578
Both can be handeld together
The text was updated successfully, but these errors were encountered: