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

<@UBAJ7TD53> was there a regression in the Kubernetes Helm provider not rendering `Input&lt;&gt;` values? I'm seeing this since updating `@pulumi/kubernetes` to 0.23:

```
    Error: render error in "[redacted]/secret.yaml": template: [redacted]/secret.yaml:15:49: executing "[redacted]/secret.yaml" at &lt;b64enc&gt;: wrong type for value; expected string; got map[string]interface {}
```

Only change was updating the Pulumi kubernetes provider.

Yes. The value it's failing on is a promise, the previous values in the chart (by lexicographic ordering) are all strings

```

    Error: render error in "[redacted]/secret.yaml": template: [redacted]/secret.yaml:15:49: executing "[redacted]/secret.yaml" at &lt;b64enc&gt;: wrong type for value; expected string; got map[string]interface {}
        at Chart.resources.allConfig.apply.cfg (/builds/[redacted]/monorepo/pulumi/node_modules/@pulumi/kubernetes/helm/v2/helm.js:112:23)
        at OutputImpl.&lt;anonymous&gt; (/builds/[redacted]/monorepo/pulumi/node_modules/@pulumi/pulumi/output.js:109:47)
        at Generator.next (&lt;anonymous&gt;)
        at fulfilled (/builds/[redacted]/monorepo/pulumi/node_modules/@pulumi/pulumi/output.js:17:58)
```

the values object is something like `values: { a: { b: async () =&gt; { return strValue; } }`

It was this:

```
new k8s.helm.v2.Chart(..., { values, ... })
```

To test this I'm trying:

```
output(values).apply(renderedValues =&gt; {
  new k8s.helm.v2.Chart(..., { values: renderedValues, ... })
})
```

this sounds like a bug. can you file an issue?

this ended up being a bug in a third-party library

If anyone else finds this, deep merging values objects using `isMergeableObject: isPlainObject`

with is-plain-object 2.x: fine
with is-plain-object 3.x: not fine