6
# Using a single workspace:
terraform {
  backend "remote" {
    hostname = "app.terraform.io"
    organization = "company"

    workspaces {
      name = "my-app-prod"
    }
  }
}

For Terraform remote backend, would there be a way to use variable to specify the organization / workspace name instead of the hardcoded values there?

The Terraform documentation didn't seem to mention anything related either.

woodykiddy
  • 6,074
  • 16
  • 59
  • 100

2 Answers2

7

The backend configuration documentation goes into this in some detail. The main point to note is this:

Only one backend may be specified and the configuration may not contain interpolations. Terraform will validate this.

If you want to make this easily configurable then you can use partial configuration for the static parts (eg the type of backend such as S3) and then provide config at run time interactively, via environment variables or via command line flags.

I personally wrap Terraform actions in a small shell script that runs terraform init with command line flags that uses an appropriate S3 bucket (eg a different one for each project and AWS account) and makes sure the state file location matches the path to the directory I am working on.

ydaetskcoR
  • 53,225
  • 8
  • 158
  • 177
3

I had the same problems and was very disappointed with the need of additional init/wrapper scripts. Some time ago I started to use Terragrunt.

It's worth taking a look at Terragrunt because it closes the gap between Terraform and the lack of using variables at some points, e.g. for the remote backend configuration: https://terragrunt.gruntwork.io/docs/getting-started/quick-start/#keep-your-backend-configuration-dry

Kevin
  • 1,232
  • 10
  • 28