From f76c49146871b297e506d9bbebb3be44ae9caa4a Mon Sep 17 00:00:00 2001 From: Nick Fagerlund Date: Wed, 26 Jun 2019 10:56:30 -0700 Subject: [PATCH] website: CLI config: Team tokens work with CLI actions (#21883) Team tokens never worked with the `atlas` backend, but the `remote` backend uses them as intended; they can perform plans and applies on workspaces where the associated team has at least plan or write permissions, respectively. --- website/docs/commands/cli-config.html.markdown | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/website/docs/commands/cli-config.html.markdown b/website/docs/commands/cli-config.html.markdown index 5687f26d13..bc1a2ebb35 100644 --- a/website/docs/commands/cli-config.html.markdown +++ b/website/docs/commands/cli-config.html.markdown @@ -81,8 +81,10 @@ The following settings can be set in the CLI configuration file: ``` ~> **Important:** The token provided here must be a - [user API token](/docs/enterprise/users-teams-organizations/users.html#api-tokens), - and not a team or organization token. + [user token](/docs/enterprise/users-teams-organizations/users.html#api-tokens) + or a + [team token](/docs/enterprise/users-teams-organizations/service-accounts.html#team-service-accounts); + organization tokens cannot be used for command-line Terraform actions. -> **Note:** The credentials hostname must match the hostname in your module sources and/or backend configuration. If your Terraform Enterprise instance