resilien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update note to be more direct :)

This commit is contained in:
Laura Pacilio 2022-01-21 10:48:27 -05:00
parent 1d53273b7a
commit 9f4c4ff093
5 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/docs/language/resources/provisioners/connection.mdx
View File

@ -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

2
website/docs/language/resources/provisioners/file.mdx
View File

@ -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

2
website/docs/language/resources/provisioners/local-exec.mdx
View File

@ -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

2
website/docs/language/resources/provisioners/null_resource.mdx
View File

@ -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

2
website/docs/language/resources/provisioners/remote-exec.mdx
View File

@ -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