Fix grammar

RK/fix-links
Rose 2 years ago
parent 1b5966dd50
commit 9babc8a1ee

@ -10,7 +10,7 @@ Required flags
external network calls. This is needed to run these tests. Without it, the
tests do not run.
* `TFE_TOKEN=<admin token>` and `TFE_HOSTNAME=<hostname>`. The helpers
for these tests require admin access to a HCP Terraform/TFE instance.
for these tests require admin access to an HCP Terraform/TFE instance.
* `-timeout=30m`. Some of these tests take longer than the default 10m timeout for `go test`.
### Flags

@ -20,5 +20,5 @@ accept the following option to modify that behavior:
remote execution environment cannot decode.
We recommend against using this option unless absolutely necessary. Overriding this check can result
in a HCP Terraform workspace that is no longer able to complete remote operations with the currently
in an HCP Terraform workspace that is no longer able to complete remote operations with the currently
selected version of Terraform.

@ -8,7 +8,7 @@ description: >-
The Terraform CLI integration with HCP Terraform lets you use HCP Terraform and Terraform Enterprise on the command line. In the documentation HCP Terraform instructions also apply to Terraform Enterprise, except where explicitly stated.
Using HCP Terraform through the command line is called the [CLI-driven run workflow](/terraform/cloud-docs/run/cli). When you use the CLI workflow, operations like `terraform plan` or `terraform apply` are remotely executed in HCP Terraform's run environment by default, with log output streaming to the local terminal. This lets you use HCP Terraform features within the familiar Terraform CLI workflow, including variables encrypted at rest in a HCP Terraform workspace, cost estimates, and policy checking.
Using HCP Terraform through the command line is called the [CLI-driven run workflow](/terraform/cloud-docs/run/cli). When you use the CLI workflow, operations like `terraform plan` or `terraform apply` are remotely executed in HCP Terraform's run environment by default, with log output streaming to the local terminal. This lets you use HCP Terraform features within the familiar Terraform CLI workflow, including variables encrypted at rest in an HCP Terraform workspace, cost estimates, and policy checking.
> **Hands On:** Try the [Migrate State to HCP Terraform](/terraform/tutorials/cloud/cloud-migrate) tutorial.

@ -76,7 +76,7 @@ The `cloud` block supports the following configuration arguments:
directory, and cannot manage workspaces from the CLI (e.g. `terraform workspace select` or
`terraform workspace new`). This option conflicts with `tags`.
- `project` - (Optional) The name of a HCP Terraform project. Workspaces that need creating
- `project` - (Optional) The name of an HCP Terraform project. Workspaces that need creating
will be created within this project. `terraform workspace list` will be filtered by workspaces
in the supplied project.
@ -103,7 +103,7 @@ Use the following environment variables to configure the `cloud` block:
- `TF_CLOUD_HOSTNAME` - The hostname of a Terraform Enterprise installation. Terraform reads this when `hostname` is omitted from the `cloud` block. If both are specified, the configuration takes precedence.
- `TF_CLOUD_PROJECT` - The name of a HCP Terraform project. Terraform reads this when `workspaces.project` is omitted from the `cloud` block. If both are specified, the cloud block configuration takes precedence.
- `TF_CLOUD_PROJECT` - The name of an HCP Terraform project. Terraform reads this when `workspaces.project` is omitted from the `cloud` block. If both are specified, the cloud block configuration takes precedence.
- `TF_WORKSPACE` - The name of a single HCP Terraform workspace. Terraform reads this when `workspaces` is omitted from the `cloud` block. HCP Terraform will not create a new workspace from this variable; the workspace must exist in the specified organization. You can set `TF_WORKSPACE` if the `cloud` block uses tags. However, the value of `TF_WORKSPACE` must be included in the set of tags. This variable also selects the workspace in your local environment. Refer to [TF_WORKSPACE](/terraform/cli/config/environment-variables#tf_workspace) for details.

@ -245,7 +245,7 @@ terraform {
}
```
After you configure the integration, a HCP Terraform API key is all your team members need to edit config and run speculative plans
After you configure the integration, an HCP Terraform API key is all your team members need to edit config and run speculative plans
against the latest version of the state file using all the remotely stored
input variables.

@ -32,7 +32,7 @@ Terraform Community Edition lets you:
## HCP Terraform
HCP Terraform is a SaaS application that runs Terraform in a stable, remote environment and securely stores state and secrets. It includes a rich user interface that helps you better understand your Terraform operations and resources, allows you to define role-based access controls, and offers a private registry for sharing modules and providers. HCP Terraform also integrates with the Terraform CLI and connects to common version control systems (VCS) like GitHub, GitLab, and Bitbucket. When you connect a HCP Terraform workspace to a VCS repository, new commits and changes can automatically trigger Terraform plans. HCP Terraform also offers an API, allowing you to integrate it into existing workflows.
HCP Terraform is a SaaS application that runs Terraform in a stable, remote environment and securely stores state and secrets. It includes a rich user interface that helps you better understand your Terraform operations and resources, allows you to define role-based access controls, and offers a private registry for sharing modules and providers. HCP Terraform also integrates with the Terraform CLI and connects to common version control systems (VCS) like GitHub, GitLab, and Bitbucket. When you connect an HCP Terraform workspace to a VCS repository, new commits and changes can automatically trigger Terraform plans. HCP Terraform also offers an API, allowing you to integrate it into existing workflows.
Many HCP Terraform features are free for small teams; we offer paid plans for larger organizations with additional collaboration and governance features.
@ -48,7 +48,7 @@ HCP Terraform lets you:
### Resources
- [Create a HCP Terraform Account](https://app.terraform.io/public/signup/account)
- [Create an HCP Terraform Account](https://app.terraform.io/public/signup/account)
- [HCP Terraform Documentation](/terraform/cloud-docs)
- [Sentinel Documentation](/terraform/cloud-docs/policy-enforcement)
- [Get Started - HCP Terraform](/terraform/tutorials/cloud-get-started) tutorials show you how to manage infrastructure using HCP Terraform's VCS integration

@ -80,7 +80,7 @@ Kubernetes is an open-source workload scheduler for containerized applications.
### Resources
- Try the [Manage Kubernetes Resources via Terraform](/terraform/tutorials/kubernetes/kubernetes-provider) tutorial. You will use Terraform to schedule and expose a NGINX deployment on a Kubernetes cluster.
- Try the [Deploy Infrastructure with the HCP Terraform Operator for Kubernetes](/terraform/tutorials/kubernetes/kubernetes-operator) tutorial. You will configure and deploy the Operator to a Kubernetes cluster and use it to create a HCP Terraform workspace and provision a message queue for an example application.
- Try the [Deploy Infrastructure with the HCP Terraform Operator for Kubernetes](/terraform/tutorials/kubernetes/kubernetes-operator) tutorial. You will configure and deploy the Operator to a Kubernetes cluster and use it to create an HCP Terraform workspace and provision a message queue for an example application.
## Parallel Environments

@ -219,7 +219,7 @@ the remote workspace accept the following option to modify that behavior:
local operation creating a new state snapshot which the workspace's
remote execution environment would then be unable to decode.
Overriding this check can result in a HCP Terraform workspace that is
Overriding this check can result in an HCP Terraform workspace that is
no longer able to complete remote operations, so we recommend against
using this option.

@ -328,7 +328,7 @@ the module where it was declared.
When variables are declared in the root module of your configuration, they
can be set in a number of ways:
* [In a HCP Terraform workspace](/terraform/cloud-docs/workspaces/variables).
* [In an HCP Terraform workspace](/terraform/cloud-docs/workspaces/variables).
* Individually, with the `-var` command line option.
* In variable definitions (`.tfvars`) files, either specified on the command line
or automatically loaded.
@ -522,7 +522,7 @@ precedence over earlier ones:
* Any `*.auto.tfvars` or `*.auto.tfvars.json` files, processed in lexical order
of their filenames.
* Any `-var` and `-var-file` options on the command line, in the order they
are provided. (This includes variables set by a HCP Terraform
are provided. (This includes variables set by an HCP Terraform
workspace.)
~> **Important:** In Terraform 0.12 and later, variables with map and object

Loading…
Cancel
Save