Luke Mallon

I've hit this issue, but if I don't run `goenv init -` then goenv doesn't work for me. My zshrc config is as follows: ``` # Check for goenv existance...

I have just moved some of my groups to subgroups because of paid features we require on gitlab.com and have come up against this issue. Other than not using glide...

Nevermind my edited comment. Setting `repo` to the git url didn't work, not sure why it appeared to work on my other machine yesterday. Running it on this machine I...

@todvora @JamesCropcho I'll try get a sample of data to you over the weekend. I'm gonna run it again myself and see how it goes. It is possible that some...

I've just installed this and I'm hitting this issue with `v0.0.38`. ```bash ❯ aws-google-auth -V aws-google-auth 0.0.38 ❯ aws-google-auth --resolve-aliases --idp-id ${IDPID} --sp-id ${SPID} --username ${GSUIT_USER} --region ${AWS_REGION} Google Password:...

Another approach here could be to use annotations to associate the runner service account with your IRSA IAM Role: ```yaml runner: serviceAccount: annotations: eks.amazonaws.com/role-arn: [aws-arn-id] ```

Ah right, sorry I forgot that the IRSA Role needs to have the name of the Service Account set. You could pass the flag `--role-only` in the eksctl command to...

@chanwit just dropping a comment here so I don't forgot, if possible we need to get hashicorp/terraform-exec#268 merged or have your fork updated to at least v0.16.0 as that is...

Another possible solution would be to have the `tf-controller` watching the `Lease`s to see if a `tf-runner` completes but fails to release the `Lease`, the `tf-controller` could then force the...

We found two issues that were the cause of this in two separate cases: ```json { "level": "error", "ts": "2022-06-15T20:14:34.824Z", "logger": "runner.terraform", "msg": "error creating the plan", "error": "exit status...