This message was deleted.

sparse-intern-71089

10/28/2023, 3:30 PM

This message was deleted.

salmon-account-74572

10/31/2023, 3:43 PM

Hmm, I can’t recreate this behavior. What version of Pulumi and what version of Node are you using? On my system it worked using Pulumi 3.91.1 with Node 18.13.0.

cuddly-magician-97620

10/31/2023, 5:10 PM

pulumi version v3.91.1 node --version v12.22.9 I guess Node upgrade to > 14 should fix that. I'll try it and respond here with the result. Thanks!

cuddly-magician-97620

11/01/2023, 4:29 PM

Confirming that the node upgrade to

v20.8.0

fixed the problem. Thanks again!

salmon-account-74572

11/01/2023, 4:51 PM

nods I suspected an older Node version might be the culprit here. Glad it’s fixed now!

cuddly-magician-97620

11/01/2023, 5:03 PM

On a related note - when I create a new project with

pulumi new aws-typescript

and then run

npm outdated

in the new project directory, it shows me the dependencies are not at the latest versions. Does that mean that upgrade of these dependencies to the latest versions in any of my existing projects is not recommended (yet)?

salmon-account-74572

11/01/2023, 6:24 PM

No. You can upgrade to newer Pulumi releases. There is a dependency between AWS and the AWSX/EKS/API Gateway components; version 1.x of those components requires AWS v5, but versions 2.x of those components works with AWS v6. The suggested versions in the “latest” field in your screenshot should be fine.

🙌 1

6 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.