Skip to content

Commit 17338fb

Browse files
Add info about Z3 instances to docs (#13052) (#9308)
[upstream:0c92f790469fb1cd55595e2e197e98f018618919] Signed-off-by: Modular Magician <[email protected]>
1 parent 83312b4 commit 17338fb

File tree

2 files changed

+6
-0
lines changed

2 files changed

+6
-0
lines changed

.changelog/13052.txt

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
```release-note:none
2+
Added info about z3 instances behavior to docs
3+
```

website/docs/r/compute_instance_template.html.markdown

+3
Original file line numberDiff line numberDiff line change
@@ -331,6 +331,9 @@ The following arguments are supported:
331331

332332
To create a machine with a [custom type](https://cloud.google.com/dataproc/docs/concepts/compute/custom-machine-types) (such as extended memory), format the value like `custom-VCPUS-MEM_IN_MB` like `custom-6-20480` for 6 vCPU and 20GB of RAM.
333333

334+
More advanced machine types like [z3](https://cloud.google.com/compute/docs/storage-optimized-machines) will
335+
create disks that cannot be managed by Terraform by default. You can account for that by using `lifecycle.ignore_changes` or adding these disks into your config.
336+
334337
- - -
335338
* `name` - (Optional) The name of the instance template. If you leave
336339
this blank, Terraform will auto-generate a unique name.

0 commit comments

Comments
 (0)