You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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/v1alpha1kind: Workspacemetadata:
name: workspacename #May be changed to optional if workspaceID is provided below.spec:
organization: FinastraworkspaceID: ws-iXXXXXXXXX #New Configuration to use existing workspaceIDsecretsMountPath: "/tmp/secrets"agentPoolID: apool-iXXXXXXXXmodule:
source: "X"version: "0.0.1"
The text was updated successfully, but these errors were encountered:
Community Note
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
The text was updated successfully, but these errors were encountered: