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
terraform-k8s & Kubernetes Version
v1.0.0
Affected Resource(s)
Terraform Configuration Files
# Copy-paste your Terraform configuration from the operator here.# To retrieve the configuration, use `kubectl -n $NAMESPACE describe configmap $WORKSPACE_NAME`
Debug Output
2021-03-19T17:53:11.033Z ERROR controller Reconciler error {"controller": "workspace-controller", "name": "tf-data", "namespace": "yarblar", "error": "Error while assigning ssh key to workspace: resource not found"}
Expected Behavior
Org token should provide enough permission for operator to run. There doesn't appear to be much granularity for resources like sshkey and agent pool but if there was this routine would only need list. Additionally this might be an issue for upstream tfc, wanted to get some advice on this?
Actual Behavior
Org tokens (at least in my findings) lack the permission to list SSH Keys.
Hey @aareet ! Thanks for the response! I'll go ahead and bring this up with our tfc contacts, maybe they can help get something tracked. Also, was there a more current slack/discord for this project? The one listed on the main page is the cncf catch all for the tf provider. Thanks again!
Community Note
terraform-k8s & Kubernetes Version
v1.0.0
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
Org token should provide enough permission for operator to run. There doesn't appear to be much granularity for resources like sshkey and agent pool but if there was this routine would only need list. Additionally this might be an issue for upstream tfc, wanted to get some advice on this?
Actual Behavior
Org tokens (at least in my findings) lack the permission to list SSH Keys.
Steps to Reproduce
Run the operator with an Org token
Important Factoids
References
https://github.com/hashicorp/terraform-k8s/blob/master/workspacehelper/tfc_org.go#L205
The text was updated successfully, but these errors were encountered: