Skip to content

Commit f30b47b

Browse files
committed
Add a link to private state page
1 parent b2d165b commit f30b47b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

website/docs/plugin/framework/resources/write-only-arguments.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,4 +109,4 @@ Since write-only arguments have no prior values, user intent or value changes ca
109109
- Pair write-only arguments with a configuration attribute (required or optional) to “trigger” the use of the write-only argument
110110
- For example, a `password_wo` write-only argument can be paired with a configured `password_wo_version` attribute. When the `password_wo_version` is modified, the provider will send the `password_wo` value to the API.
111111
- Use a keepers attribute (which is used in the [Random Provider](https://registry.terraform.io/providers/hashicorp/random/latest/docs#resource-keepers)) that will take in arbitrary key-pair values. Whenever there is a change to the `keepers` attribute, the provider will use the write-only argument value.
112-
- Use the resource's [private state] to store secure hashes of write-only argument values, the provider will then use the hash to determine if a write-only argument value has changed in later Terraform runs.
112+
- Use the resource's [private state](/terraform/plugin/framework/resources/private-state) to store secure hashes of write-only argument values, the provider will then use the hash to determine if a write-only argument value has changed in later Terraform runs.

0 commit comments

Comments
 (0)