Add support for terraform_remote_state

[leg100]

A user cannot use terraform_remote_state to reference the state of OTF workspaces.

Currently, OTF issues the terraform process with a "run token", which only has permissions to access the OTF module registry, for the retrieval of child modules during a terraform init. it does not have permissions to access any other endpoints on OTF, including the state endpoints which would allow terraform_remote_state to succeed.

TFC by default does not share state with other workspaces but does provide the option to open up access workspace by workspace, or to the entire organization:

This is perhaps something that could be adopted by OTF.

[Spritekin]

Interesting. But maybe you can test this, I know its not the same but maybe it works:

a. issue a full access token. The same token a user would use to access the OTF API.

b. Use the token like this:

data "terraform_remote_state" "oss_prod" {
  backend = "remote"

  config = {
    hostname = "otf.oss.ossy.dev"
    token = var.token
    organization = "Spritekin"
    workspaces = {
      name = "my-workspace"
    }
  }
}

Just as a worksround while you solve this problem.

[take-five]

It would be nice if OTF supported it out of the box. We're currently looking if OTF can be used within our organization - we use state sharing quite a lot and this is a blocker