Chanwit Kaewkasi

Thank you @darrylweaver Currently we're still relying on K8s asynchronous reconciliation to do deletion. To make everything deleted in the right order, we would need to adopt an algorithm from,...

The technical stuff behind this scenario is quite complex. So I'm explaining here again: Initially, we have a chain of Terraform objects with dependencies: ``` (A) | (B) | (C)...

yep, I agreed. we're planning to support this kind of code generation and inspection. in the mean time, we have a feature called `break-the-glass` to help you troubleshoot your problems....

would love to try it. maybe you could introduce it to this project by porting just one simple e2e case and we would evaluate them together.

Some users reported that it once worked. Maybe you could try: ``` spec: backendConfig: customConfiguration: "{}" ``` to see what would happen with the latest version of Terraform binary we...

To improve the semantics of `backendConfig.disable`, here's my proposal: ``` backendConfig: disable: true ``` Would no longer affect the cloud config and set `backendConfig.customConfiguration` to `# no override` to allow...

Hi @rattboi, that's our internal team label. We now have an umbrella issue to address the resource-deletion process of the Terraform Controller as a whole here: https://github.com/weaveworks/tf-controller/issues/755

Thank you @eloo-abi for your suggestion. Would you mind drafting the output you'd like to see as a simple code block here?

Got it. That was helpful. So they are basically some information from the original TF resource.

This project is now rebooted and landed to the new home, which is 100% community driven. We're now prioritizing OpenTofu support so any contributions are welcome!