Unable to be used with terraform workspaces about terraform-aws-tfstate-backend HOT 2 OPEN

Instead of setting enabled to false, since you're working with workspaces you can have the default workspace house the state for the backend, and after bootstrap work simply with other workspaces. Then, set enabled as follows:

module "terraform_state_backend" {
  enabled = terraform.workspace == "default"
  source  = "cloudposse/tfstate-backend/aws"
  version = "0.38.1"
  # ...
}

This way, the module will set the count argument of every resource block it uses to 0, turning them into no-ops. Additionally, if you want to avoid provisioning infrastructure of your own save for the one supporting the S3+DynamoDB backend, you can separate the rest of your configuration into a module and use count:

module "rest_of_my_config" {
  # Avoid creating anything within if we're in the default workspace.
  count = terraform.workspace == "default" ? 0 : 1
  # ...
}

from terraform-aws-tfstate-backend.

The module creates an S3 backend to be used by Terraform. Usually this is done once per company/organization, so I do not understand why you are trying to create one per workspace.

Whether or not you are using workspaces, it is your responsibility to ensure you are not creating duplicate resources by using different inputs for different instantiations of this module. This module provides several inputs you can use to vary the name of created resources:

• namespace
• tenant
• environment
• stage
• name
• attributes

from terraform-aws-tfstate-backend.