Skip to content
This repository was archived by the owner on Nov 20, 2024. It is now read-only.
This repository was archived by the owner on Nov 20, 2024. It is now read-only.

Use Existing Terraform Cloud Workspace #127

Open
@joshvermast

Description

@joshvermast

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

The ability to define a Terraform Cloud Workspace to be utilized by Terraform Cloud Operator instead of having it create it's own workspace. This would alleviate the problem of Admin level permission token being required for every instance of Terraform Cloud Operator.

There may have to be consideration taken that the targetted Workspace have no stored State at the time of binding to a TFCO CR.

Potential Terraform Configuration

---
apiVersion: app.terraform.io/v1alpha1
kind: Workspace
metadata:
  name: workspacename #May be changed to optional if workspaceID is provided below.
spec:
  organization: Finastra
  workspaceID: ws-iXXXXXXXXX #New Configuration to use existing workspaceID
  secretsMountPath: "/tmp/secrets"
  agentPoolID: apool-iXXXXXXXX
  module:
    source: "X"
    version: "0.0.1"

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions