Add Future Reservations capabilities to 'google_compute_reservation' provider

[scott-whitbread-db]

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 an issue is assigned to a user, that user is claiming responsibility for the issue.
• Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Description

Recently, Google released new features in reservations that allows users to make 'Future Reservations' for Google Compute Engine (GCE) resources via the usual methods (console, gcloud, REST). This request is to add in these new features and fields for future reservations into the existing terraform resource (google_compute_reservation).

More details on Future Reservations can be found here - https://cloud.google.com/compute/docs/instances/future-reservations-overview

New or Affected Resource(s)

google_compute_reservation

Potential Terraform Configuration

References

b/303690299

[SarahFrench]

Note from triage: the Beta version of the Compute API separates futureReservations from reservations, the latter being what google_compute_reservation manages. This suggests a new resource google_compute_future_reservation would be needed: https://cloud.google.com/compute/docs/reference/rest/beta/futureReservations