@@ -104,7 +104,7 @@ As mentionned in GitLab's documentation, that requires that your Terraform scrip
Terraform [HTTP backend](https://www.terraform.io/docs/language/settings/backends/http.html), the templates
does the rest to configure it automatically.
This default behavior can be disabled by setting `$TF_GITLAB_BACKEND_DISABLED` to `false`.
This default behavior can be disabled by setting `$TF_GITLAB_BACKEND_DISABLED` to `true`.
In that case, you'll have to declare and configure your backend and tfstate by yourself (see [Implicit Backend configuration support](#implicit-backend-configuration-support) below).
#### _Error acquiring the state lock_ workaround
@@ -159,7 +159,7 @@ terraform init \
#### Implicit Backend configuration support
If you disabled the GitLab-managed Terraform state (by setting `$TF_GITLAB_BACKEND_DISABLED` to `false`),
If you disabled the GitLab-managed Terraform state (by setting `$TF_GITLAB_BACKEND_DISABLED` to `true`),
the template supports an implicit [backend configuration](https://www.terraform.io/language/settings/backends/configuration#file) mechanism:
1. Looks for a `$env.tfbackend` file (ex: `staging.tfbackend` for staging environment),