You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Example Usage - Enabling hierarchical namespace
107
+
108
+
```hcl
109
+
resource "google_storage_bucket" "auto-expire" {
110
+
name = "hns-enabled-bucket"
111
+
location = "US"
112
+
force_destroy = true
113
+
114
+
hierarchical_namespace = {
115
+
enabled = true
116
+
}
117
+
}
118
+
```
119
+
106
120
## Argument Reference
107
121
108
122
The following arguments are supported:
@@ -157,6 +171,8 @@ The following arguments are supported:
157
171
158
172
*`soft_delete_policy` - (Optional, Computed) The bucket's soft delete policy, which defines the period of time that soft-deleted objects will be retained, and cannot be permanently deleted. If the block is not provided, Server side value will be kept which means removal of block won't generate any terraform change. Structure is [documented below](#nested_soft_delete_policy).
159
173
174
+
*`hierarchical_namespace` - (Optional, ForceNew) The bucket's hierarchical namespace policy, which defines the bucket capability to handle folders in logical structure. Structure is [documented below](#nested_hierarchical_namespace).
*`action` - (Required) The Lifecycle Rule's action configuration. A single block of this type is supported. Structure is [documented below](#nested_action).
@@ -269,6 +285,12 @@ The following arguments are supported:
269
285
270
286
*`effective_time` - (Computed) Server-determined value that indicates the time from which the policy, or one with a greater retention, was effective. This value is in RFC 3339 format.
0 commit comments