-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
plugin crash: panic: interface conversion: interface {} is nil, not map[string]interface {} #120
Comments
I can confirm this is an issues with v2.0.4 (reverting to v2.0.3 fixes the issue). |
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 |
A workaround for this is to set stringData to |
@joaocc thanks for reporting. Do you have a reproduction code by any chance? |
I can try to find it in the history of state files. However, when diagnosing this, I noticed i was doing the following:
|
By default the stringData is not being set in terraform state file on 2.0.3, so this might be a bit of an edge case (I guess you were constructing yaml manifest via hcl objects?) I even tried with
and it gives following state file
@joaocc struggling to get a test case triggering the issue. Having said that, I found a potential error but would love to test it with the panic before releasing it (since its a bit of an edge case as I mentioned) |
Yes, I am building the YAML objects via HCL + yamlencode. |
Ok, I will try to make some further tests later on (maybe jumping from the gavin original provider towards 2.0.4). |
Hi.
I think this illustrates the example of null stringData
If you need more data pls let me know how to send privately. |
same here, I've just migrated from gavinbunney/kubectl. Downgraded to 2.0.3 and it worked |
Hey do you have an idea of when this change will get merged? I'd like to use one of the features that came out with v2.0.4. Also good work on the fix! |
After upgrading to provider v2.0.4, we started getting this error.
This was code that didn't change recently, so not 100% sure if this is transient, was there in 2.0.3 (with something else), or is indeed from 2.0.4 (which works well elsewhere in the same code.
The text was updated successfully, but these errors were encountered: