Chanwit Kaewkasi

Thank you for reporting @dejwsz I'll have a look

Our current execution model does not allow that as it's fully synchronous. To do so, we have to change the execution model to be asynchronous, which is doable but more...

Yes, of course.

Have you tried? ```yaml spec: runnerPodTemplate: spec: env: - name: TF_LOG value: "true" ``` Let me know if it's still not working for you.

I see. Then we cannot support that too. But we have another flag for you to try. https://github.com/weaveworks/tf-controller/blob/main/runner/server.go#L202 Hope it's useful a bit.

`spec.logging: info # debug` would be possible, but I could see some security concerns. https://github.com/weaveworks/tf-controller/blob/b7c13da914c0240eb4aec1a905a080385b9fc37f/runner/server.go#L198-L205

We shall add this as the "observabilities" item to the roadmap.

Thank you for reporting this @mjazwiecki > What did I miss? Nop, I think it's definitely a bug.

@mjazwiecki did you just happen to upgrade from the previous version, and you got the old CRD inside the cluster? It seems to me that the value of `.customConfiguration` didn't...

Sorry for not being clear. I meant the old version of the TF-controller and its chart.