This message was deleted.

sparse-intern-71089

07/16/2019, 12:39 PM

This message was deleted.

white-balloon-205

07/16/2019, 1:50 PM

This is a bug - if you could open an issue to track, that would be great. I believe it will only happen if you have two different versions of

@pulumi/Pulumi

in your program, and the parent resource was using the older version while the child was using the newer. If you can update your versions to be consistent, I believe that would allow you to workaround this in the meantime.

rapid-eye-32575

07/16/2019, 2:06 PM

Hey @white-balloon-205, that's a great tip. I will try to see if any versions differ (though that was my first idea and I thought I did harmonize the version 😉 ). Should I still open a GitHub issue even if the cause is just version inconsistencies?

white-balloon-205

07/16/2019, 2:12 PM

Yes - an issue would still be useful so we can prevent this from being a problem even when there are mismatched versions.

rapid-eye-32575

07/16/2019, 2:15 PM

Alright, will create one then once I narrowed this down 👍

rapid-eye-32575

07/16/2019, 2:51 PM

Hmm I somehow fixed it by deleting all

node_modules

-directories and running

yarn

again. Fixing the version inconsistencies in the

package.json

files and running

yarn

alone did not help 🤷

rapid-eye-32575

07/16/2019, 2:59 PM

Here's the issue I created on that topic: https://github.com/pulumi/pulumi/issues/2938

white-balloon-205

07/16/2019, 6:19 PM

Thanks. This is fixed now with https://github.com/pulumi/pulumi/pull/2942.

rapid-eye-32575

07/17/2019, 8:02 AM

Wow, that was fast 🙂

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.