Remove overview page and update notes on provisioner pages

This commit is contained in:
Laura Pacilio 2022-01-05 11:08:33 -05:00 committed by Martin Atkins
parent 6dcf00aefc
commit fc4ceedc6d
10 changed files with 34 additions and 35 deletions

View File

@ -11,7 +11,8 @@ The `chef` provisioner installs, configures and runs the Chef Client on a remote
resource. The `chef` provisioner supports both `ssh` and `winrm` type resource. The `chef` provisioner supports both `ssh` and `winrm` type
[connections](/language/resources/provisioners/connection). [connections](/language/resources/provisioners/connection).
!> **Note:** This provisioner was removed in the 0.15.0 version of Terraform after being deprecated as of Terraform 0.13.4. For most common situations there are better alternatives to using provisioners. For more information, see [the main Provisioners page](/language/resources/provisioners). !> **Warning:** This provisioner was removed in the 0.15.0 version of Terraform after being deprecated as of Terraform 0.13.4. For most common situations there are better alternatives to using provisioners. Refer to
[Declaring Provisioners](/language/resources/provisioners/syntax) for more details.
## Requirements ## Requirements

View File

@ -11,19 +11,10 @@ Most provisioners require access to the remote resource via SSH or WinRM, and
expect a nested `connection` block with details about how to connect. expect a nested `connection` block with details about how to connect.
-> **Note:** Provisioners should only be used as a last resort. For most -> **Note:** Provisioners should only be used as a last resort. For most
common situations there are better alternatives. For more information, see common situations there are better alternatives. Refer to
[the main Provisioners page](/language/resources/provisioners). [Declaring Provisioners](/language/resources/provisioners/syntax) for more details.
-> **Note:** In Terraform 0.11 and earlier, providers could set default values ## Connection Block
for some connection settings, so that `connection` blocks could sometimes be
omitted. This feature was removed in 0.12 in order to make Terraform's behavior
more predictable.
-> **Note:** Since the SSH connection type is most often used with
newly-created remote resources, validation of SSH host keys is disabled by
default. In scenarios where this is not acceptable, a separate mechanism for
key distribution could be established and the `host_key` directive documented
below explicitly set to verify against a specific key or signing CA.
Connection blocks don't take a block label, and can be nested within either a Connection blocks don't take a block label, and can be nested within either a
`resource` or a `provisioner`. `resource` or a `provisioner`.
@ -37,6 +28,18 @@ One use case for providing multiple connections is to have an initial
provisioner connect as the `root` user to set up user accounts, and have provisioner connect as the `root` user to set up user accounts, and have
subsequent provisioners connect as a user with more limited permissions. subsequent provisioners connect as a user with more limited permissions.
Since the SSH connection type is most often used with
newly-created remote resources, validation of SSH host keys is disabled by
default. In scenarios where this is not acceptable, a separate mechanism for
key distribution could be established and the `host_key` directive documented
below explicitly set to verify against a specific key or signing CA.
-> **Note:** In Terraform 0.11 and earlier, providers could set default values
for some connection settings, so that `connection` blocks could sometimes be
omitted. This feature was removed in 0.12 in order to make Terraform's behavior
more predictable.
## Example usage ## Example usage
```hcl ```hcl

View File

@ -13,8 +13,8 @@ executing Terraform to the newly created resource. The `file` provisioner
supports both `ssh` and `winrm` type [connections](/language/resources/provisioners/connection). supports both `ssh` and `winrm` type [connections](/language/resources/provisioners/connection).
-> **Note:** Provisioners should only be used as a last resort. For most -> **Note:** Provisioners should only be used as a last resort. For most
common situations there are better alternatives. For more information, see common situations there are better alternatives. Refer to
[the main Provisioners page](/language/resources/provisioners). [Declaring Provisioners](/language/resources/provisioners/syntax) for more details.
## Example usage ## Example usage

View File

@ -9,7 +9,8 @@ description: >-
The `habitat` provisioner installs the [Habitat](https://habitat.sh) supervisor and loads configured services. This provisioner only supports Linux targets using the `ssh` connection type at this time. The `habitat` provisioner installs the [Habitat](https://habitat.sh) supervisor and loads configured services. This provisioner only supports Linux targets using the `ssh` connection type at this time.
!> **Note:** This provisioner was removed in the 0.15.0 version of Terraform after being deprecated as of Terraform 0.13.4. For most common situations there are better alternatives to using provisioners. For more information, see [the main Provisioners page](/language/resources/provisioners). !> **Warning:** This provisioner was removed in the 0.15.0 version of Terraform after being deprecated as of Terraform 0.13.4. For most common situations there are better alternatives to using provisioners. Refer to
[Declaring Provisioners](/language/resources/provisioners/syntax) for more details.
## Requirements ## Requirements

View File

@ -1,12 +0,0 @@
---
page_title: Provisioners Overview - Configuration Language
description: >-
Provisioners model specific actions on a local or remote machine to prepare
servers or other infrastructure for service.
---
# Provisioners
Provisioners can be used to model specific actions on the local machine or on a
remote machine in order to prepare servers or other infrastructure objects for
service.

View File

@ -19,8 +19,8 @@ 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. system services such as `sshd` may not be started yet on compute resources.
-> **Note:** Provisioners should only be used as a last resort. For most -> **Note:** Provisioners should only be used as a last resort. For most
common situations there are better alternatives. For more information, see common situations there are better alternatives. Refer to
[the main Provisioners page](/language/resources/provisioners). [Declaring Provisioners](/language/resources/provisioners/syntax) for more details.
## Example usage ## Example usage

View File

@ -19,6 +19,10 @@ details](/language/resources/provisioners/connection) on a `null_resource`. You
use its `triggers` argument and any meta-arguments to control exactly where in use its `triggers` argument and any meta-arguments to control exactly where in
the dependency graph its provisioners will run. the dependency graph its provisioners will run.
-> **Note:** Provisioners should only be used as a last resort. For most
common situations there are better alternatives. Refer to
[Declaring Provisioners](/language/resources/provisioners/syntax) for more details.
## Example usage ## Example usage
```hcl ```hcl

View File

@ -11,7 +11,8 @@ The `puppet` provisioner installs, configures and runs the Puppet agent on a
remote resource. The `puppet` provisioner supports both `ssh` and `winrm` type remote resource. The `puppet` provisioner supports both `ssh` and `winrm` type
[connections](/language/resources/provisioners/connection). [connections](/language/resources/provisioners/connection).
!> **Note:** This provisioner was removed in the 0.15.0 version of Terraform after being deprecated as of Terraform 0.13.4. For most common situations there are better alternatives to using provisioners. For more information, see [the main Provisioners page](/language/resources/provisioners). !> **Warning:** This provisioner was removed in the 0.15.0 version of Terraform after being deprecated as of Terraform 0.13.4. For most common situations there are better alternatives to using provisioners. Refer to
[Declaring Provisioners](/language/resources/provisioners/syntax) for more details.
## Requirements ## Requirements

View File

@ -18,8 +18,8 @@ provisioner requires a [connection](/language/resources/provisioners/connection)
and supports both `ssh` and `winrm`. and supports both `ssh` and `winrm`.
-> **Note:** Provisioners should only be used as a last resort. For most -> **Note:** Provisioners should only be used as a last resort. For most
common situations there are better alternatives. For more information, see common situations there are better alternatives. Refer to
[the main Provisioners page](/language/resources/provisioners). [Declaring Provisioners](/language/resources/provisioners/syntax) for more details.
## Example usage ## Example usage
@ -27,7 +27,7 @@ common situations there are better alternatives. For more information, see
resource "aws_instance" "web" { resource "aws_instance" "web" {
# ... # ...
# Establishes connection to be used by all # Establishes connection to be used by all
# generic remote provisioners (i.e. file/remote-exec) # generic remote provisioners (i.e. file/remote-exec)
connection { connection {
type = "ssh" type = "ssh"

View File

@ -12,7 +12,8 @@ Type: `salt-masterless`
The `salt-masterless` Terraform provisioner provisions machines built by Terraform The `salt-masterless` Terraform provisioner provisions machines built by Terraform
using [Salt](http://saltstack.com/) states, without connecting to a Salt master. The `salt-masterless` provisioner supports `ssh` [connections](/language/resources/provisioners/connection). using [Salt](http://saltstack.com/) states, without connecting to a Salt master. The `salt-masterless` provisioner supports `ssh` [connections](/language/resources/provisioners/connection).
!> **Note:** This provisioner was removed in the 0.15.0 version of Terraform after being deprecated as of Terraform 0.13.4. For most common situations there are better alternatives to using provisioners. For more information, see [the main Provisioners page](/language/resources/provisioners). !> **Warning:** This provisioner was removed in the 0.15.0 version of Terraform after being deprecated as of Terraform 0.13.4. For most common situations there are better alternatives to using provisioners. Refer to
[Declaring Provisioners](/language/resources/provisioners/syntax) for more details.
## Requirements ## Requirements