Add "repeat_interval" schedule option to google_storage_transfer_job

[burnzy]

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

The storage transfer API has a "repeat interval" field for the schedule options. This option allows transfer jobs to repeat as frequently as 1 hour, instead of the default 24 hour interval. This is very useful for when transfers need to be scheduled to run more frequently than just once per day.

When left unset, the API will default to a 24 hour repeat interval (which is the current terraform behaviour)

New or Affected Resource(s)

• google_storage_transfer_job

Potential Terraform Configuration

The schedule block of the resource would need to support a new parameter like "repeat_interval" such as below:

schedule {
  repeat_interval = "3600s"
}

References

• https://cloud.google.com/storage-transfer/docs/reference/rest/v1/transferJobs#schedule

[psvaiter]

This is an important missing configuration that's already supported by google_bigquery_data_transfer_config resource but not by this one.

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