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

Some of my tests have just started failing -- they had been running a few days ago, last time I touched this repository. The problem is caused by the random.RandomString resource, which is not hitting the `newResource()` callback in `setMocks()`. Has this changed? Tracing into the constructor looks like a normal Pulumi resource, but newResource() doesn't get called at any point.

The end result is that `new RandomString().result` is an Output containing undefined, because I have been setting `result` in `newResource()`. So all my other resources that use `result` now have undefineds, and the related assertions all fail.