Michael Wojcikiewicz
Michael Wojcikiewicz
We just ran into this exact issue, using that EKS TF Module too. A workaround that seems to work: 1) Create the new subnets, setup the routes, etc 2) Manually...
Having same issue, only inside a module. TF 0.15.3 and 1.10.0 provider
FYI I have a hackey workaround. Basically, I create a submodule that is its own state, that all it does it use the `flux` provider to generate the Manifest YAML...
Here's a work around I found for setting deeply nested values less painfully (tf 12+ only) ``` resource helm_release my-app { name = "my-app" namespace = "my-app-ns" chart = "/path/to/chart"...