<!-- Hi there, Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html. If your issue relates to a specific Terraform provider, please open it in the provider's own repository. The index of providers is at https://github.com/terraform-providers . --> ### Terraform Version <!--- Run `terraform -v` to show the version, and paste the result between the ``` marks below. If you are not running the latest version of Terraform, please try upgrading because your issue may have already been fixed. --> Tested on: ``` 0.11.14 0.12.6 through 0.12.23 ``` ### Terraform Configuration Files <!-- Paste the relevant parts of your Terraform configuration between the ``` marks below. For large Terraform configs, please use a service like Dropbox and share a link to the ZIP file. For security, you can also encrypt the files using our GPG public key. --> ```hcl locals { test = file("${terraform.workspace}.txt") } ``` ### Debug Output <!-- Full debug output can be obtained by running Terraform with the environment variable `TF_LOG=trace`. Please create a GitHub Gist containing the debug output. Please do _not_ paste the debug output in the issue, since debug output is long. Debug output may contain sensitive information. Please review it before posting publicly, and if you are concerned feel free to encrypt the files using the HashiCorp security public key. --> https://gist.github.com/Rycieos/735a509ab62bcc4bb997e743e7187bde ### Crash Output <!-- If the console output indicates that Terraform crashed, please share a link to a GitHub Gist containing the output of the `crash.log` file. --> ### Expected Behavior <!-- What should have happened? --> Because `terraform validate` is a "stateless" command (see https://www.terraform.io/docs/commands/validate.html), it will not evaluate the `terraform.workspace` identifier, and will say that the configuration is valid (even though the file doesn't exist). ### Actual Behavior <!-- What actually happened? --> `terraform validate` evaluates the `"${terraform.workspace}.txt"` string as `"default.txt"`, and calls the `file()` function, which fails because the file does not exist. ### Steps to Reproduce <!-- Please list the full steps required to reproduce the issue, for example: 1. `terraform init` 2. `terraform apply` --> `terraform init` `terraform validate` ### Additional Context <!-- Are there anything atypical about your situation that we should know? For example: is Terraform running in a wrapper script or in a CI system? Are you passing any unusual command line options or environment variables to opt-in to non-default behavior? --> `terraform validate` is supposed to ignore variables, but it doesn't ignore `terraform.workspace`. For a full setup of why this is a problem, consider a module where there are other workspaces than `default` that are used, and `default` is not used (because you can't delete the `default` workspace): `terraform init` `terraform workspace new test` `touch test.txt` `terraform validate` This works `terraform workspace select default` `terraform validate` This doesn't We are running into this issue because the docs claim `validate` is stateless, so we are validating right after running `terraform init`, not bothering to checkout a workspace that we normally use first. ### References <!-- Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example: - #6017 -->