This message was deleted.

sparse-intern-71089

11/30/2018, 5:19 PM

This message was deleted.

bitter-oil-46081

11/30/2018, 7:04 PM

Okay, @cold-coat-35200, this is pretty gross but I think it will unblock you. Can you edit

~/.pulumi/bin/pulumi-resource-pulumi-nodejs

to look like this:

Copy code

#!/bin/sh
node $(node -e "console.log(require.resolve('@pulumi/pulumi/cmd/dynamic-provider'))") $@

The change here is that instead of the relative path, we now use

$(node -e "console.log(require.resolve('@pulumi/pulumi/cmd/dynamic-provider'))")

to construct the path where the dymanic provider's launcher is, which will allow node to use its normal resolution semantics. I believe that will address your issue, based on my local testing it does for me.

bitter-oil-46081

11/30/2018, 7:19 PM

I opened https://github.com/pulumi/pulumi/issues/2261 to track making the actual fix, but I'd love to know it addresses your issue first.

cold-coat-35200

11/30/2018, 8:15 PM

thanks @bitter-oil-46081, I can check it tomorrow

bitter-oil-46081

12/01/2018, 1:43 AM

Awesome. Thanks!

cold-coat-35200

12/01/2018, 4:14 PM

it solved the issue, at least for the preview, I can't run the actual update right now, but assume it will be ok, thanks @bitter-oil-46081

bitter-oil-46081

12/01/2018, 6:59 PM

Thanks. I’ll get this into master on Monday.

bitter-oil-46081

12/06/2018, 10:31 PM

@cold-coat-35200 Just an FYI, I released a new version of the CLI (0.16.7) that has this fix. Thanks for reporting the issue!

cold-coat-35200

12/07/2018, 5:56 AM

thanks @bitter-oil-46081

95 Views

Open in Slack

Previous Next

Pulumi Community

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.