millions-furniture-7540205/19/2020, 2:03 PM
recursively, so even if I specify
in package.json, they’ll be removed. • https://www.pulumi.com/docs/tutorials/aws/serializing-functions/#determining-the-appropriate-node-modules-packages-to-include-with-a-lambda • https://github.com/pulumi/pulumi/blob/master/sdk/nodejs/runtime/closure/codePaths.ts#L296-L300 Being able to run the lambda with the mysql provider would be preferred, but it seems I’m forced to look into other possible solutions, which are more complex. Other Possible Solutions: 1. Publish a lambda with an external tool, and call it as an existing lambda with pulumi (messy, requires more than
). 2. Use mysql nodejs package to create the database (that stinks, I have a MySQL provider). 3. In addition to GitHub Actions, use AWS Code Services so the pipeline can run in the VPC (redundant). 4. Run either a mysql, or pulumi container in fargate that can provision the databases (seems like a lot more infra and complexity to create databases). Maybe I’m missing something obvious here. Hoping someone can shed some light on how I should approach this problem, and maybe other opportunities I’ve overlooked. Thanks, loving Pulumi so far!
as perhaps a dynamic provider. Not a better idea than what you've come up with
millions-furniture-7540205/19/2020, 3:36 PM
busy-umbrella-3606705/19/2020, 5:46 PM