Skip to content

Add more details about terraform.tfvars #158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
annawinkler merged 1 commit into from
Oct 5, 2022
Merged

Add more details about terraform.tfvars #158

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions website/docs/cloud-docs/workspaces/variables/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,9 +99,15 @@ For example, if you apply `A_Variable_Set` and `B_Variable_Set` to the same work

Non-global variable sets always take precedence over global variable sets that are applied to all workspaces within an organization. Terraform does not allow global variable sets to contain variables with the same key, so they cannot conflict.

### 6. `auto.tfvars` Variable Files
### 6. `*.auto.tfvars` Variable Files

Variables in the Terraform Cloud workspace and variables provided through the command line always overwrite variables with the same key from files ending in `auto.tfvars`.
Variables in the Terraform Cloud workspace and variables provided through the command line always overwrite variables with the same key from files ending in `.auto.tfvars`.

### 7. `terraform.tfvars` Variable File

Variables in the `.auto.tfvars` files take precedence over variables in the `terraform.tfvars` file.

-> **Note:** Although Terraform Cloud uses variables from `terraform.tfvars`, Terraform Enterprise currently ignores this file.

### Precedence Example

Expand Down