website: update "atlas" backend to recommend using ATLAS_TOKEN environment variable

This commit is contained in:
Kevin Fishner 2017-12-05 11:34:05 -08:00 committed by Martin Atkins
parent d6b8e27086
commit 3538f832b0
1 changed files with 3 additions and 5 deletions

View File

@ -12,8 +12,8 @@ description: |-
Stores the state in [Terraform Enterprise](https://www.terraform.io/docs/providers/index.html).
You can create a new environment in the
Environments section and generate new token in the Tokens page under Settings.
You can create a new workspace in the
Workspaces section and generate new token in the Tokens page under Settings.
~> **Why is this called "atlas"?** Atlas was previously a commercial offering
from HashiCorp that included a full suite of enterprise products. The products
@ -27,7 +27,6 @@ Enterprise**. While this transition is in progress, you may see references to
terraform {
backend "atlas" {
name = "bigbang/example"
access_token = "foo"
}
}
```
@ -42,7 +41,6 @@ data "terraform_remote_state" "foo" {
backend = "atlas"
config {
name = "bigbang/example"
access_token = "X2iTFefU5aWOjg.atlasv1.YaDa"
}
}
```
@ -52,5 +50,5 @@ data "terraform_remote_state" "foo" {
The following configuration options / environment variables are supported:
* `name` - (Required) Full name of the environment (`<username>/<name>`)
* `access_token` / `ATLAS_TOKEN` - (Required) Terraform Enterprise API token
* `ATLAS_TOKEN`/ `access_token` - (Required) Terraform Enterprise API token. It is recommended that `ATLAS_TOKEN` is set as an environment variable rather than using `access_token` in the configuration.
* `address` - (Optional) Address to alternative Terraform Enterprise location (Terraform Enterprise endpoint)