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
Copy file name to clipboardExpand all lines: docs/content/reference/field.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,12 +107,11 @@ Example:
107
107
sensitive: true
108
108
```
109
109
110
-
### `write_only`
111
-
Set to true to enable write-only functionality for this field.
112
-
If true, the write-only fields will be automatically generated by the code generator (`<field_name>_wo` and `<field_name>_wo_version`).
113
-
When the write-only variant of a field is used, it means that its value will be obscured in Terraform output as well as not be stored in state.
114
-
This field is meant to replace `sensitive` as it doesn't store the value in state.
115
-
See [Ephemerality in Resources - Use Write-only arguments](https://developer.hashicorp.com/terraform/language/resources/ephemeral/write-only) for more information.
110
+
### `write_only_legacy` (deprecated)
111
+
If true, the field is considered "write-only", which means that its value will
112
+
be obscured in Terraform output as well as not be stored in state. This field is meant to replace `sensitive` as it doesn't store the value in state.
113
+
See [Ephemerality in Resources - Use Write-only arguments](https://developer.hashicorp.com/terraform/language/resources/ephemeral/write-only)
114
+
for more information.
116
115
117
116
Write-only fields are only supported in Terraform v1.11+. Because the provider supports earlier Terraform versions, write only fields must be paired with (mutually exclusive) `sensitive` fields covering the same functionality for compatibility with those older versions.
118
117
This field cannot be used in conjuction with `immutable` or `sensitive`.
@@ -122,9 +121,11 @@ This field cannot be used in conjuction with `immutable` or `sensitive`.
122
121
Example:
123
122
124
123
```yaml
125
-
write_only: true
124
+
write_only_legacy: true
126
125
```
127
126
127
+
**Deprecated**: This field is deprecated and will be removed in a future release.
128
+
128
129
### `ignore_read`
129
130
If true, the provider sets the field's value in the resource state based only
130
131
on the user's configuration. If false or unset, the provider sets the field's
0 commit comments