docs: google terraform storage bucket versioning #32041
Conversation
| @@ -4,17 +4,29 @@ columns: | |||
|
|
|||
| rows: | |||
| - "Terraform version": | | |||
|
|
|||
|
|
|||
There was a problem hiding this comment.
kay-kim
force-pushed
the
docs-google-terraform-next
branch
from
47336b7 to
1884b23
Compare
| @@ -71,6 +71,13 @@ In addition, the default [`node_group_instance_types`] has changed from | |||
|
|
|||
| {{</ tabs >}} | |||
|
|
|||
| ## Storage bucket versioning | |||
There was a problem hiding this comment.
kay-kim
force-pushed
the
docs-google-terraform-next
branch
from
1884b23 to
ee11eb7
Compare
kay-kim
force-pushed
the
docs-google-terraform-next
branch
from
ee11eb7 to
28b10fb
Compare
| Starting in v0.2.1 of Materialize on GCP Terraform, storage bucket versioning is | ||
| disabled to facilitate cleanup of resources during testing. When running in | ||
| production, versioning should be turned on with a sufficient TTL to meet any | ||
| data-recovery requirements. | ||
|
|
There was a problem hiding this comment.
In the referenced pr I did decide to enable versioning with a TTL of 7 days for non active versions, but make this configurable. This is a middle ground that more easily allows one to test without versioning enabled while maintaining the preferred production setting.
There was a problem hiding this comment.
👍 will do a patch tomorrow.
There was a problem hiding this comment.
So ... apparently, "tomorrow" is "next week" 😄 .
In any case, it's still disabled, yes? (I see the default is false) it's just that the ttl default value is set to 7.
There was a problem hiding this comment.
oh yeah, sorry I think I waffled on this a few times thanks for reading closely!!!
kay-kim
force-pushed
the
docs-google-terraform-next
branch
from
28b10fb to
ec6d628
Compare
kay-kim
merged commit 614bc14
into
MaterializeInc:self-managed-docs/v25.1
reference docs update per MaterializeInc/terraform-google-materialize#22