<@UB89GSWCF> this is ready for review (and should ...
# atmos-dev
e
@Andriy Knysh (Cloud Posse) this is ready for review (and should probably be manually tested as well). One thing we're missing from the documentation, is how the backend path configuration (at least for S3 backend) should be updated when workspaces are disabled. Otherwise all environments will use the same workspace, which will be very bad. https://github.com/cloudposse/atmos/pull/1073
🙌 1
merged 1
Specifically, I'm talking about what changes should be made here, when workspaces are disabled:
Copy code
terraform:
  backend_type: s3  # s3, remote, vault, azurerm, gcs, cloud
  backend:
    s3:
      acl: "bucket-owner-full-control"
      encrypt: true
      bucket: "your-s3-bucket-name"
      dynamodb_table: "your-dynamodb-table-name"
      key: "terraform.tfstate"
      region: "your-aws-region"
      role_arn: "arn:aws:iam::xxxxxxxx:role/terraform-backend-read-write"
👀 1
I think something related to key prefix
@Andriy Knysh (Cloud Posse) unfortunately, I made these comments here, instead of the PR
I see we merged the PR
We should document that if disabling the workspace, the
key_prefix
for S3 should be used instead