CLI Error: workspaces not supported

[phazel]

Terraform Version

Terraform v0.12.10
+ provider.aws v2.32.0

Terraform Configuration Files

credentials "app.terraform.io" {
  token = "AAAAAAAAAAA.something.BBBBBBBBBBBBBBBBBBBBBBBBBBB"
}

Debug Output

https://gist.github.com/phazel/1da824f34ef0f3a4d4481b1c83b17549

Crash Output

Expected Behavior

List of existing workspaces, which at this point should have just been 'default'. Also creation of new workspace.

Actual Behavior

workspaces not supported error

Steps to Reproduce

1. Set up terraform repo, state, and resources in AWS
2. Set up remote state in Terraform Cloud
3. Attempt to list workspaces and add a new one

Additional Context

I've set up remote state in Terraform Cloud, and I've currently got my infra resources set up in one AWS account. I'm trying to use workspaces to set up the same collection of resources in another AWS environment, using workspaces. Given that TF Cloud has workspaces and recommends creating new ones for each environment, it seemed to me like things had moved from the previous model of one backend holding the state for all workspaces. Is this assumption correct? Is workspaces still the right tool for this? Is there some incompatibility between workspaces in the cli and Terraform Cloud workspaces?

References

This issue might also be relevant:
#22035

[phazel]

Solved: I needed to use prefix for my backend configuration, to allow multiple backends/workspaces.

# Using multiple workspaces:
terraform {
  backend "remote" {
    hostname = "app.terraform.io"
    organization = "company"

    workspaces {
      prefix = "my-app-"
    }
  }
}

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.