Commit 007f3b17 authored by Bishop's avatar Bishop Committed by Marcin Sedlak-Jakubowski

Minor doc corrections in terraform_state.html

parent 63f41d6e
...@@ -17,7 +17,7 @@ to securely store the state files in local storage (the default) or ...@@ -17,7 +17,7 @@ to securely store the state files in local storage (the default) or
WARNING: WARNING:
Using local storage (the default) on clustered deployments of GitLab will result in Using local storage (the default) on clustered deployments of GitLab will result in
a split state across nodes, making subsequent executions of Terraform inconsistent. a split state across nodes, making subsequent executions of Terraform inconsistent.
You are highly advised to use a remote storage in that case. You are highly advised to use a remote storage resource in that case.
The GitLab managed Terraform state backend can store your Terraform state easily and The GitLab managed Terraform state backend can store your Terraform state easily and
securely, and spares you from setting up additional remote resources like securely, and spares you from setting up additional remote resources like
...@@ -28,7 +28,7 @@ Amazon S3 or Google Cloud Storage. Its features include: ...@@ -28,7 +28,7 @@ Amazon S3 or Google Cloud Storage. Its features include:
- Locking and unlocking state. - Locking and unlocking state.
- Remote Terraform plan and apply execution. - Remote Terraform plan and apply execution.
A GitLab **administrator** must [setup the Terraform state storage configuration](../../../administration/terraform_state.md) A GitLab **administrator** must [set up the Terraform state storage configuration](../../../administration/terraform_state.md)
before using this feature. before using this feature.
## Permissions for using Terraform ## Permissions for using Terraform
...@@ -89,7 +89,7 @@ local machine, this is a simple way to get started: ...@@ -89,7 +89,7 @@ local machine, this is a simple way to get started:
``` ```
If you already have a GitLab-managed Terraform state, you can use the `terraform init` command If you already have a GitLab-managed Terraform state, you can use the `terraform init` command
with the prepopulated parameters values: with the pre-populated parameters values:
1. On the top bar, select **Menu > Projects** and find your project. 1. On the top bar, select **Menu > Projects** and find your project.
1. On the left sidebar, select **Infrastructure > Terraform**. 1. On the left sidebar, select **Infrastructure > Terraform**.
...@@ -300,7 +300,7 @@ any changes that are required for your infrastructure. All Terraform commands ...@@ -300,7 +300,7 @@ any changes that are required for your infrastructure. All Terraform commands
should now work. should now work.
If you ever set or change modules or backend configuration for Terraform, If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other re-run this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary. commands will detect it and remind you to do so if necessary.
``` ```
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment