github.com/kanishk98/terraform@v1.3.0-dev.0.20220917174235-661ca8088a6a/website/docs/cli/cloud/settings.mdx (about)

     1  ---
     2  page_title: Terraform Cloud Settings - Terraform CLI
     3  description: >-
     4    Configure the Terraform Cloud CLI integration.
     5  ---
     6  
     7  # Terraform Cloud Settings
     8  
     9  Terraform CLI can integrate with Terraform Cloud, acting as a client for Terraform Cloud's
    10  [CLI-driven run workflow](/cloud-docs/run/cli).
    11  
    12  > **Hands On:** Try the [Migrate State to Terraform Cloud](https://learn.hashicorp.com/tutorials/terraform/cloud-migrate) tutorial.
    13  
    14  You must configure the following settings to use Terraform Cloud for a particular working directory:
    15  
    16  - Provide credentials to access Terraform Cloud, preferably by using the
    17    [`terraform login`](/cli/commands/login) command.
    18  - Add a `cloud` block to the directory's Terraform configuration, to specify
    19    which organization and workspace(s) to use.
    20  - Optionally, use a `.terraformignore` file to specify files that shouldn't be
    21    uploaded with the Terraform configuration when running plans and applies.
    22  
    23  After adding or changing a `cloud` block, you must run `terraform init`.
    24  
    25  ## The `cloud` Block
    26  
    27  The `cloud` block is a nested block within the top-level `terraform` settings
    28  block. It specifies which Terraform Cloud workspaces to use for the current
    29  working directory.
    30  
    31  ```hcl
    32  terraform {
    33    cloud {
    34      organization = "my-org"
    35      hostname = "app.terraform.io" # Optional; defaults to app.terraform.io
    36  
    37      workspaces {
    38        tags = ["networking", "source:cli"]
    39      }
    40    }
    41  }
    42  ```
    43  
    44  The `cloud` block also has some special restrictions:
    45  
    46  - A configuration can only provide one `cloud` block.
    47  - A `cloud` block cannot be used with [state backends](/language/settings/backends).
    48    A configuration can use one or the other, but not both.
    49  - A `cloud` block cannot refer to named values (like input variables, locals, or
    50    data source attributes).
    51  
    52  The `cloud` block only affects Terraform CLI's behavior. When Terraform Cloud uses a configuration
    53  that contains a cloud block - for example, when a workspace is configured to use a VCS provider
    54  directly - it ignores the block and behaves according to its own workspace settings.
    55  
    56  ### Arguments
    57  
    58  The `cloud` block supports the following configuration arguments:
    59  
    60  - `organization` - (Required) The name of the organization containing the
    61    workspace(s) the current configuration should use.
    62  
    63  - `workspaces` - (Required) A nested block that specifies which remote Terraform Cloud workspaces to
    64    use for the current configuration. The `workspaces` block must contain **exactly one** of the
    65    following arguments, each denoting a strategy for how workspaces should be mapped:
    66  
    67    - `tags` - (Optional) A set of Terraform Cloud workspace tags. You will be able to use
    68      this working directory with any workspaces that have all of the specified tags,
    69      and can use [the `terraform workspace` commands](/cli/workspaces)
    70      to switch between them or create new workspaces. New workspaces will automatically have
    71      the specified tags. This option conflicts with `name`.
    72  
    73    - `name` - (Optional) The name of a single Terraform Cloud workspace. You will
    74      only be able to use the workspace specified in the configuration with this working
    75      directory, and cannot manage workspaces from the CLI (e.g. `terraform workspace select` or
    76      `terraform workspace new`). This option conflicts with `tags`.
    77  
    78  - `hostname` - (Optional) The hostname of a Terraform Enterprise installation, if using Terraform
    79    Enterprise. Defaults to Terraform Cloud (app.terraform.io).
    80  
    81  - `token` - (Optional) The token used to authenticate with Terraform Cloud.
    82    We recommend omitting the token from the configuration, and instead using
    83    [`terraform login`](/cli/commands/login) or manually configuring
    84    `credentials` in the
    85    [CLI config file](/cli/config/config-file#credentials).
    86  
    87  ### Environment Variables
    88  
    89  -> **Note:** CLI integration environment variables are supported in Terraform v1.2.0 and later.
    90  
    91  You can use environment variables to configure one or more `cloud` block attributes. This is helpful when you want to configure Terraform as part of a Continuous Integration (CI) pipeline. Terraform only reads these variables if the corresponding attribute is omitted from your configuration file. If you choose to configure the `cloud` block entirely through environment variables, you must still add an empty `cloud` block in your configuration file.
    92  
    93  ~> **Warning:** Remote execution with non-interactive workflows requires auto-approved deployments. Minimize risk of unpredictable infrastructure changes and configuration drift by making sure that no one can change your infrastructure outside of your automated build pipeline.  Refer to [Non-Interactive Workflows](/cloud-docs/run/cli#non-interactive-workflows) for details.
    94  
    95  Use the following environment variables to configure the `cloud` block:
    96  
    97  - `TF_CLOUD_ORGANIZATION` - The name of the organization. Terraform reads this variable when `organization` omitted from the `cloud` block`. If both are specified, the configuration takes precedence.
    98  
    99  - `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 precendence.
   100  
   101  - `TF_WORKSPACE` - The name of a single Terraform Cloud workspace. Terraform reads this when `workspaces` is omitted from the `cloud` block. Terraform Cloud 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](https://www.terraform.io/cli/config/environment-variables#tf_workspace) for details.
   102  
   103  ## Excluding Files from Upload with .terraformignore
   104  
   105  When executing a remote `plan` or `apply` in a [CLI-driven run](/cloud-docs/run/cli),
   106  a copy of your configuration directory is uploaded to Terraform Cloud. You can define
   107  paths to exclude from upload by adding a `.terraformignore` file at the root of your
   108  configuration directory. If this file is not present, the upload will exclude
   109  the following by default:
   110  
   111  - `.git/` directories
   112  - `.terraform/` directories (exclusive of `.terraform/modules`)
   113  
   114  The rules in `.terraformignore` file resemble the rules allowed in a
   115  [.gitignore file](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring):
   116  
   117  - Comments (starting with `#`) or blank lines are ignored.
   118  - End a pattern with a forward slash `/` to specify a directory.
   119  - Negate a pattern by starting it with an exclamation point `!`.
   120  
   121  -> **Note:** Unlike `.gitignore`, only the `.terraformignore` at the root of the configuration directory is considered.