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

I'm wondering if I can replace my function with a no-op or something else that doesn't involve serializing async functions? Unfortunately I'm currently using _aws.cloudwatch.EventRuleEventSubscription_, which is very handy but wraps the offending code inside Pulumi.

If anyone else has an example of a working test of a resource that includes something like a Function or an EventRuleEventSubscription, I might be able to figure out what I can change to make my code work...

Hi <@U012UJTT55M>,
  Does the following <https://www.pulumi.com/docs/tutorials/aws/aws-ts-scheduled-function/|Scheduled Function on AWS> help as it has `EventRuleEventSubscription` <https://github.com/pulumi/examples/blob/master/aws-ts-scheduled-function/index.ts#L40|here>

No, I have all that working, it's going great. My problem is when I have that sort of code in a component resource, and a Mocha test instantiates the resource, then the Pulumi innards get confused. It looks like there's a Promise rejected somewhere in the Pulumi internals, and then every subsequent test keeps spewing Promise rejections and it's all bad.

Oddly, the tests don't fail.. but they're not usable in this state.