Terraform Cloud remote state: add allowing a prefix/suffix for organization parameter

[binlab]

Current Terraform Version

Terraform v0.12.28

Use-cases

For top-level security reasons - each Workspace e.g. Production, Staging, Development etc in a separate organization with a suffix with an appropriate environment e.g. myOrganization-Production, myOrganization-Staging etc.

Proposal

Would be nice to have the possibility configuring the prefix/suffix of the organization by workspace. For security reasons (state file storing a piece of sensitive information) we want to split different environments by high level (e.g. like it advises by Amazon - each environment in separate AWS account). Now we can't grant permission for some group of people only for e.g. a Staging environment without allowing permission to see a Production environment.

For now this not allowed:

terraform {
  backend "remote" {
    hostname     = "app.terraform.io"
    organization = format("myOrganization-%s", terraform.workspace)
    workspaces {
      name = "aws"
    }
  }
}

fails with an errors:

$ terraform init 
Initializing modules...

Initializing the backend...
Backend configuration changed!

Terraform has detected that the configuration specified for the backend
has changed. Terraform will now check for existing state in the backends.

Error: Function calls not allowed

  on main.tf line 4, in terraform:
   4:     organization = format("myOrganization-%s", terraform.workspace)

Functions may not be called here.

[binlab]

@apparentlymart are there any updates according to this issue?
seems like this a related issue #13022