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

Are you on Node 12 perhaps? There’s a recent issue causing “hangs” with a recent Node 12 version. 

If so, can you try downgrading to Node 10 (the current LTS version) and see if you get the same issue?

Yea, I can try that. I am on Node 12, but I thought the issue was Catalina only lol

Ok, switching to node v10 with nvm works. brew has node 12 as "stable" which was the issue

Thanks for confirming. Yea, we initially thought it was limited to Catalina but doesn’t seem to be. 

We are tracking this in <https://github.com/pulumi/pulumi/issues/3309>.

Hmm - we are seeing our GKE up script hang as well.

Yep - switching back to node 10 seems to fix the issue for us

<@UD8SD7MQQ>.  I'm working on a fix for this now.  Question: do you ever call `new aws.Provider(...)` anywhere in your project?

I think it might be ``` return gcp.container.getEngineVersions({
        location: gcp.config.zone,
        versionPrefix: config.k8sVersion,
    });```

That's fine.  My fix will be most likely to work if you are *not* doing `new aws.Provider()` anywhere.

we also have EKS deployments.. let me check

you can potentially try to unblock yourself now by passing in `{ async: true }` to `getEngineVersions`.  however, you will have to deal with result coming back as a Promise.

my fix should make it so that your above code now works without a hang.