https://pulumi.com logo
p

purple-appointment-43233

10/08/2019, 10:55 PM
Hey all, I’m returning to a stack that I haven’t used in a few weeks and Pulumi seems to be hanging indefinitely on a call to
aws.route53.getZone({ name: domainParts.parentDomain }).then(zone => zone.id)
. This is a copy & paste (and very lightly edited) version of the published example on deploying a static website to S3. Any thoughts as to what could be going on? The only thing I can think of that materially changed was that I upgraded to catalina, and had to upgrade some node packages to get it to build…
g

gentle-diamond-70147

10/08/2019, 11:05 PM
Can you provide the full cli output you're seeing?
p

purple-appointment-43233

10/08/2019, 11:09 PM
Copy code
Type                 Name                      Plan        Info
     pulumi:pulumi:Stack  analytics-web-production  running     ASSUMING ZONE <http://sub.mydomain.com|sub.mydomain.com>. EXISTS
Which comes from a code snippet that looks like:
Copy code
const domainParts = getDomainAndSubdomain(config.targetDomain);
    console.log(`ASSUMING ZONE ${domainParts.parentDomain} EXISTS`);
    const hostedZoneId = aws.route53.getZone({ name: domainParts.parentDomain }).then(zone => zone.id);
    console.log("Fetched zone");
So grpc has problems on Catalina, though I’m not exactly sure what or why, but I had to blow away my yarn.lock to get anything to even run (grpc fails to build). Here’s the diff of the new yarn.lock: https://gist.github.com/loganb/6df360e2c42d0945ebfe2db7ce80d7a2
g

gentle-diamond-70147

10/08/2019, 11:19 PM
which version of node are you using?
p

purple-appointment-43233

10/08/2019, 11:20 PM
Copy code
$ node --version
v12.11.1
I’m also using a ~6 month old version of this example: https://github.com/pulumi/examples/blame/master/aws-ts-static-website/index.ts
Notably, two months ago the line that is blocking for me was changed to “use synchronous data sources” (mine uses a promise), https://github.com/pulumi/examples/blame/master/aws-ts-static-website/index.ts#L101
g

gentle-diamond-70147

10/08/2019, 11:28 PM
Looks like an issue with Catalina and Node 12. I'm seeing the same thing. I'm opening an issue now. Downgrading to Node 10 (LTS) should resolve it.
p

purple-appointment-43233

10/08/2019, 11:28 PM
k, I’ll try that for now, thx
g

gentle-diamond-70147

10/08/2019, 11:31 PM