mirror of
https://github.com/hashicorp/terraform.git
synced 2026-05-28 04:03:27 -04:00
Fix punctuation and spelling errors in Basic CLI Features and Command: plan documentation (#32791)
* Update index.mdx * Update index.mdx * Update plan.mdx
This commit is contained in:
parent
a56264b792
commit
287cfd1490
2 changed files with 7 additions and 7 deletions
|
|
@ -63,7 +63,7 @@ All other commands:
|
|||
Global options (use these before the subcommand, if any):
|
||||
-chdir=DIR Switch to a different working directory before executing the
|
||||
given subcommand.
|
||||
-help Show this help output, or the help for a specified subcommand.
|
||||
-help Show this help output or the help for a specified subcommand.
|
||||
-version An alias for the "version" subcommand.
|
||||
```
|
||||
|
||||
|
|
@ -74,7 +74,7 @@ To get specific help for any specific command, use the `-help` option with the
|
|||
relevant subcommand. For example, to see help about the "validate" subcommand
|
||||
you can run `terraform validate -help`.
|
||||
|
||||
The inline help built in to Terraform CLI describes the most important
|
||||
The inline help built into Terraform CLI describes the most important
|
||||
characteristics of each command. For more detailed information, refer to each
|
||||
command's page for details.
|
||||
|
||||
|
|
@ -136,7 +136,7 @@ terraform -uninstall-autocomplete
|
|||
|
||||
The Terraform CLI commands interact with the HashiCorp service
|
||||
[Checkpoint](https://checkpoint.hashicorp.com/) to check for the availability
|
||||
of new versions and for critical security bulletins about the current version.
|
||||
of new versions and critical security bulletins about the current version.
|
||||
|
||||
One place where the effect of this can be seen is in `terraform version`, where
|
||||
it is used by default to indicate in the output when a newer version is
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ to be taken.
|
|||
If you are using Terraform directly in an interactive terminal and you expect
|
||||
to apply the changes Terraform proposes, you can alternatively run
|
||||
[`terraform apply`](/terraform/cli/commands/apply) directly. By default, the "apply" command
|
||||
automatically generates a new plan and prompts for you to approve it.
|
||||
automatically generates a new plan and prompts you to approve it.
|
||||
|
||||
You can use the optional `-out=FILE` option to save the generated plan to a
|
||||
file on disk, which you can later execute by passing the file to
|
||||
|
|
@ -132,7 +132,7 @@ In addition to alternate [planning modes](#planning-modes), there are several op
|
|||
resource instance with the given address. This is helpful when one or more remote objects have become degraded, and you can use replacement objects with the same configuration to align with immutable infrastructure patterns. Terraform will use a "replace" action if the specified resource would normally cause an "update" action or no action at all. Include this option multiple times to replace several objects at once. You cannot use `-replace` with the `-destroy` option, and it is only available from Terraform v0.15.2 onwards. For earlier versions, use [`terraform taint`](/terraform/cli/commands/taint) to achieve a similar result.
|
||||
|
||||
- `-target=ADDRESS` - Instructs Terraform to focus its planning efforts only
|
||||
on resource instances which match the given address and on any objects that
|
||||
on resource instances that match the given address and on any objects that
|
||||
those instances depend on.
|
||||
|
||||
-> **Note:** Use `-target=ADDRESS` in exceptional circumstances only, such as recovering from mistakes or working around Terraform limitations. Refer to [Resource Targeting](#resource-targeting) for more details.
|
||||
|
|
@ -161,8 +161,8 @@ root module.
|
|||
|
||||
However, to do so will require writing a command line that is parsable both
|
||||
by your chosen command line shell _and_ Terraform, which can be complicated
|
||||
for expressions involving lots of quotes and escape sequences. In most cases
|
||||
we recommend using the `-var-file` option instead, and write your actual values
|
||||
for expressions involving lots of quotes and escape sequences. In most cases,
|
||||
we recommend using the `-var-file` option instead, and writing your actual values
|
||||
in a separate file so that Terraform can parse them directly, rather than
|
||||
interpreting the result of your shell's parsing.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue