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"...
/ok to test ee29372652a2114118e2b9c56d719d7ebdecce2e
/ok to test 518bb1f7f272d399f113de233bbb8e59ffacf2c7
/ok to test 47652b01ff036d64f447a6af0f9f724a8c0f2091
/ok to test 5c8f311aa4f62378d153934aaf3215b9651c96cb
/ok to test 1130e28397277897efd11b539ef05d781d1a256b