Luke Mallon

To expand on the above I'm looking at adding the following to the `spec`: ```yaml spec: backendConfig: state: forceUnlock: [holder-id] ``` By default, and following the same path as Terraform,...

I have changed the above noted structure as it impacts the `backendConfig` in a way that seems to complicate it more than I'd like. So I've moved `spec.backendConfig.state` out to...

Thanks for the feedback 👍 > There are a few things to improve UX. > - I would change `terraformState` to `tfstate` so users would be able to reason that...

Closing as #268 has been merged!

Is it something worth exploring? I could see this happening with upgrades as well

@chanwit would it make sense to have the controller check the version of the running container for the runner pod when it tries to get it and then if the...

We could look at exposing the `Terraform.SetLog` ([here](https://github.com/hashicorp/terraform-exec/blob/c3eeeea58419c22fda4600718d2a5245884af5ad/tfexec/terraform.go#L144)) and related functions in some way.

@daveoy it's not that we are blocking them, I understand it that the tf-exec package blocks them so that they can be set by that package exclusively. In order to...

This can be done with the service account but currently both service accounts use the same `imagePullSecrets` value. Might be good to have another one for the runner but fall...

Is it worth having a build container that runs all the make targets? That way the versions are in control and not relying on other peoples systems.