search

hashicorp / terraform-provider-google

Terraform Provider for Google Cloud Platform
https://registry.terraform.io/providers/hashicorp/google/latest/docs
Mozilla Public License 2.0
2.36k stars 1.75k forks source link

Does the description of the `availability_type` field on `google_alloydb_instance` need to be updated? #16483

Open SarahFrench opened 1 year ago

SarahFrench commented 1 year ago

(I'm raising this question on behalf of a customer)

https://github.com/hashicorp/terraform-provider-google/blob/adad0083a54713eedff133dc3cbd78ccd5707797/website/docs/r/alloydb_instance.html.markdown?plain=1#L215-L223

Is this description of the google_alloydb_instance resource's availability_type field still accurate? I've been responding to a customer ticket where they're confused about how this field should behave.

For example when I've been experimenting with provisioning Alloy DB resources I've found that I can provision a primary instance that is zonal, and this contradicts the line "Only READ_POOL instance supports ZONAL type":

Screenshot 2023-11-09 at 02 14 04

IPL-3850

b/322317508

melinath commented 10 months ago

It looks like the API docs for this field now read:

Availability type of an Instance. If empty, defaults to REGIONAL for primary instances. For read pools, availabilityType is always UNSPECIFIED. Instances in the read pools are evenly distributed across available zones within the region (i.e. read pools with more than one node will have a node in at least two zones).

The terraform docs seem outdated.