Joao C Costa
                                            Joao C Costa
                                        
                                    I can confirm this is an issues with v2.0.4 (reverting to v2.0.3 fixes the issue). Looking at other similar errors, it seems some resources have an empty/null field instead of...
And a bit more digging in stack trace vs code for v2.0.4 and comparing with the context of the state file, we find that there is indeed a `"stringData": null`...
A workaround for this is to set stringData to `coalesce(something.myStringData, {})` in v2.0.3 and then upgrade to v2.0.4.
I can try to find it in the history of state files. However, when diagnosing this, I noticed i was doing the following: * with provider v2.0.3, creating a manifest...
Yes, I am building the YAML objects via HCL + yamlencode. Unfortunately I don't think I will be able to get one of the original outputs :S
Hi. I have new repro of this, with 2.0.4 loading some older state file ``` { "module": "module.mmmmm1[0].module.configs[\"pa-0\"]", "mode": "managed", "type": "kubectl_manifest", "name": "this", "provider": "provider[\"registry.terraform.io/alekc/kubectl\"]", "instances": [ { "index_key":...