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

Hey Luke, i don't believe this is something we've seen before.  can you open an issue on pulumi/awsx about this and i'll try to get to it asap next week.  Thanks!

hi Cyrus, thanks for the response.

i started writing up an issue for this and in the process did a fresh `npm install` to try and reproduce the issue. to my surprise, everything worked!

it turns out 1.3.1 of pulumi had been released since I tried on Friday which contains a revert of a previous change. The changelog reads:

&gt; - Revert “propagate resource inputs to resource state during preview”. These changes had a critical issue that needs further investigation.

I reinstalled 1.3.0 and the error occurred as expected, so looks like the ‘critical issue’ mentioned above was likely the cause of my problem too.

In any case, looks like everything is working now, so I won’t submit an issue.