google_compute_snapshot does not support setting storage_locations

[jen20]

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 GCP API call compute::disks::createSnapshot has a field named storageLocations which allows the caller to specify whether the snapshot will be regional or multi-regional. If this is not set, the behaviour appears to be to create a snapshot in the nearest multi-region (at least for the US and Europe, I haven't tried this in regions which do not form part of a multi-region, like Australia).

New or Affected Resource(s)

• google_compute_snapshot

Potential Terraform Configuration

resource "google_compute_snapshot" "snapshot" {
        name = "snapshot-name"
        source_disk = "source-disk-name"
        zone = "us-west1-a" # This is the source disk zone

        storage_locations = ["us-west1"]
}

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!