No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I brought down my stack with `pulumi destroy`, and now i can't bring it up any more, i just get
```
Error: Unexpected struct type.
```
any idea what the problem might be? diagnostic messages are unhelpful, it only shows points in pulumi libraries.

And is that the whole error - or do you get more?

typescript. the whole thing:
```
Diagnostics:
  pulumi:pulumi:Stack (cfm-dev):
    error: Running program '/home/chuck/le-codes/cfm-pulumi' failed with an unhandled exception:
    Error: Unexpected struct type.
        at Function.proto.google.protobuf.Value.fromJavaScript (/home/chuck/le-codes/cfm-pulumi/node_modules/google-protobuf/google/protobuf/struct_pb.js:846:13)
        at Function.proto.google.protobuf.Struct.fromJavaScript (/home/chuck/le-codes/cfm-pulumi/node_modules/google-protobuf/google/protobuf/struct_pb.js:912:51)
        at Function.proto.google.protobuf.Value.fromJavaScript (/home/chuck/le-codes/cfm-pulumi/node_modules/google-protobuf/google/protobuf/struct_pb.js:842:55)
        at Function.proto.google.protobuf.Struct.fromJavaScript (/home/chuck/le-codes/cfm-pulumi/node_modules/google-protobuf/google/protobuf/struct_pb.js:912:51)
        at Object.&lt;anonymous&gt; (/home/chuck/le-codes/cfm-pulumi/node_modules/@pulumi/pulumi/runtime/resource.js:409:43)
        at Generator.next (&lt;anonymous&gt;)
        at fulfilled (/home/chuck/le-codes/cfm-pulumi/node_modules/@pulumi/pulumi/runtime/resource.js:17:58)
```

This is <https://github.com/pulumi/pulumi/issues/2962>.  We have a fix in progress at <https://github.com/pulumi/pulumi/pull/3069>.

I believe this will only happen on initial preview - if you use `--skip-preview` you ay be able to work around it.

oh, interesting. it seems to be caused by secretizing the kubeconfig as that other user mentioned.

and it does seem you're right that skipping the preview works