From 9f4c4ff093828b5ba54e9bd8a58c5dd07ad6a95c Mon Sep 17 00:00:00 2001 From: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com> Date: Fri, 21 Jan 2022 10:48:27 -0500 Subject: [PATCH] Update note to be more direct :) --- website/docs/language/resources/provisioners/connection.mdx | 2 +- website/docs/language/resources/provisioners/file.mdx | 2 +- website/docs/language/resources/provisioners/local-exec.mdx | 2 +- website/docs/language/resources/provisioners/null_resource.mdx | 2 +- website/docs/language/resources/provisioners/remote-exec.mdx | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/website/docs/language/resources/provisioners/connection.mdx b/website/docs/language/resources/provisioners/connection.mdx index 5b3d275ee..736d4eab3 100644 --- a/website/docs/language/resources/provisioners/connection.mdx +++ b/website/docs/language/resources/provisioners/connection.mdx @@ -10,7 +10,7 @@ description: >- Most provisioners require access to the remote resource via SSH or WinRM and expect a nested `connection` block with details about how to connect. -~> **Important:** You should only use provisioners as a last resort. There are better alternatives for most situations. Refer to +~> **Important:** Use provisioners as a last resort. There are better alternatives for most situations. Refer to [Declaring Provisioners](/language/resources/provisioners/syntax) for more details. ## Connection Block diff --git a/website/docs/language/resources/provisioners/file.mdx b/website/docs/language/resources/provisioners/file.mdx index 7b541363c..8d8b2ac04 100644 --- a/website/docs/language/resources/provisioners/file.mdx +++ b/website/docs/language/resources/provisioners/file.mdx @@ -12,7 +12,7 @@ The `file` provisioner is used to copy files or directories from the machine executing Terraform to the newly created resource. The `file` provisioner supports both `ssh` and `winrm` type [connections](/language/resources/provisioners/connection). -~> **Important:** You should only use provisioners as a last resort. There are better alternatives for most situations. Refer to +~> **Important:** Use provisioners as a last resort. There are better alternatives for most situations. Refer to [Declaring Provisioners](/language/resources/provisioners/syntax) for more details. ## Example usage diff --git a/website/docs/language/resources/provisioners/local-exec.mdx b/website/docs/language/resources/provisioners/local-exec.mdx index dee5d2081..eda7f9ad0 100644 --- a/website/docs/language/resources/provisioners/local-exec.mdx +++ b/website/docs/language/resources/provisioners/local-exec.mdx @@ -18,7 +18,7 @@ Note that even though the resource will be fully created when the provisioner is run, there is no guarantee that it will be in an operable state - for example system services such as `sshd` may not be started yet on compute resources. -~> **Important:** You should only use provisioners as a last resort. There are better alternatives for most situations. Refer to +~> **Important:** Use provisioners as a last resort. There are better alternatives for most situations. Refer to [Declaring Provisioners](/language/resources/provisioners/syntax) for more details. ## Example usage diff --git a/website/docs/language/resources/provisioners/null_resource.mdx b/website/docs/language/resources/provisioners/null_resource.mdx index cf4218086..fc270e364 100644 --- a/website/docs/language/resources/provisioners/null_resource.mdx +++ b/website/docs/language/resources/provisioners/null_resource.mdx @@ -19,7 +19,7 @@ details](/language/resources/provisioners/connection) on a `null_resource`. You use its `triggers` argument and any meta-arguments to control exactly where in the dependency graph its provisioners will run. -~> **Important:** You should only use provisioners as a last resort. There are better alternatives for most situations. Refer to +~> **Important:** Use provisioners as a last resort. There are better alternatives for most situations. Refer to [Declaring Provisioners](/language/resources/provisioners/syntax) for more details. ## Example usage diff --git a/website/docs/language/resources/provisioners/remote-exec.mdx b/website/docs/language/resources/provisioners/remote-exec.mdx index dc96b1760..769ba72de 100644 --- a/website/docs/language/resources/provisioners/remote-exec.mdx +++ b/website/docs/language/resources/provisioners/remote-exec.mdx @@ -17,7 +17,7 @@ into a cluster, etc. To invoke a local process, see the `local-exec` provisioner requires a [connection](/language/resources/provisioners/connection) and supports both `ssh` and `winrm`. -~> **Important:** You should only use provisioners as a last resort. There are better alternatives for most situations. Refer to +~> **Important:** Use provisioners as a last resort. There are better alternatives for most situations. Refer to [Declaring Provisioners](/language/resources/provisioners/syntax) for more details. ## Example usage