From 9150a1bb75b729bc24c00a0e3ab2837e86eedd12 Mon Sep 17 00:00:00 2001 From: Brian Flad Date: Tue, 21 Mar 2023 09:51:40 -0400 Subject: [PATCH] website: Minor fixes to Provisioners Without a Resource page Some details about `null_resource` were not updated with the transition to `terraform_data`. --- .../docs/language/resources/provisioners/null_resource.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/language/resources/provisioners/null_resource.mdx b/website/docs/language/resources/provisioners/null_resource.mdx index eab3322dfc..16c897a1e1 100644 --- a/website/docs/language/resources/provisioners/null_resource.mdx +++ b/website/docs/language/resources/provisioners/null_resource.mdx @@ -8,13 +8,13 @@ description: >- # Provisioners Without a Resource If you need to run provisioners that aren't directly associated with a specific -resource, you can associate them with a `null_resource`. +resource, you can associate them with a `terraform_data`. Instances of [`terraform_data`](/terraform/language/resources/terraform-data) are treated like normal resources, but they don't do anything. Like with any other resource type, you can configure [provisioners](/terraform/language/resources/provisioners/syntax) and [connection details](/terraform/language/resources/provisioners/connection) on a -`terraform_data` resource. You can also use its `triggers` argument and any +`terraform_data` resource. You can also use its `input` argument, `triggers_replace` argument, and any meta-arguments to control exactly where in the dependency graph its provisioners will run.