Using Pulumi with Typescript, if I make a typo in some variable name or make some silly syntax mistake I get this obscure error message (regardless of what the problem is) instead of the expected error message pointing to the actual error:

TypeError: Cannot convert object to primitive value
        at process.uncaughtHandler (/home/ubuntu/infra/node_modules/@pulumi/cmd/run/run.ts:305:65)
        at process.emit (node:events:531:35)
        at process.emit (/home/ubuntu/infra/node_modules/source-map-support/source-map-support.js:516:21)
        at emit (node:internal/process/promises:150:20)
        at processPromiseRejections (node:internal/process/promises:284:27)
        at processTicksAndRejections (node:internal/process/task_queues:96:32)

any ideas ?

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hello guys, we use the package @Pulumi/terraform for referencing terraform state in our typescript pulumi program. In the last few days during pulumi preview we getting error: unsupported checkable object kind "var". Do you have a similar experience or a workaround for how to fix that? we use latest version of terraform and pulumi.

This message was deleted.

Question about

pulumi up --refresh

: can anyone describe what

--refresh

does or point me to some documentation that explains it? The description in the CLI documentation isn't particularly detailed:

Refresh the state of the stack's resources before this update

I keep running into situations where I need to use the

--refresh

option with

pulumi up

or the updates are not applied correctly and the all of my Deployment resources are nonexistent after the stack is updated. I'm trying to understand why, when I need to to use

--refresh

, and whether I should always default to using

--refresh

when applying stack updates with

pulumi up

.

Can I create a CRD and use it in the same

pulumi up

run ? I created a

helm.v3.Release

for cert-manager, and a

yaml.v2.ConfigGroup

that defines a

ClusterIssuer

(cert-manager helm release installs the

ClusterIssuer

CRD) . I have a.

depends_on

in the ConfigGroup to wait for the cert-manager helm release to complete. But it seems that pulumi tries to determine if

ClusterIssuer

is a namespaced or not before the helm release actually installed the CRD. (

Exception: marshaling properties: awaiting input property "resources": failed to determine if the following GVK is namespaced: <http://cert-manager.io/v1|cert-manager.io/v1>, Kind=ClusterIssuer

) I've created a https://github.com/pulumi/pulumi-kubernetes/issues/3176 but then I realized that maybe this known already ? or there is another way to make it wait?

This message was deleted.