This message was deleted.

sparse-intern-71089

06/13/2023, 11:36 PM

This message was deleted.

billowy-army-68599

06/14/2023, 12:04 AM

hey Connor, sad to hear you’re migrating off the pulumi cloud backend. That said, there shouldn’t be any difference for lambda functions. What error are you seeing?

billowy-needle-66127

06/14/2023, 2:04 AM

I haven't used

aws.lambda.CallbackFunction

specifically, but we just moved from pulumi cloud to self-managed state and didn't have any issues across a dozen or so stacks and hundreds of resources.

happy-advantage-79856

06/14/2023, 10:10 PM

I actually have it working fine now, I have no idea why it was performing that way before. I am noticing that deployment seems to be much slower using an s3 bucket. Are there any settings that can help with this? I’ve tried increasing maxParallel, which seems like it might help a little. I’m not sure what the bottleneck would be here.

clever-sunset-76585

06/15/2023, 2:59 PM

I am noticing that deployment seems to be much slower using an s3 bucket.

How many resources do you have in your stack? Were all the resources slower to deploy?

I’ve tried increasing maxParallel, which seems like it might help a little. I’m not sure what the bottleneck would be here.

Interesting. What value did you use?

happy-advantage-79856

06/16/2023, 2:52 PM

I tried 10 and also 3, neither made a significant difference after testing it again.

clever-sunset-76585

06/16/2023, 3:02 PM

I believe the default value is max parallelism already.

2 Views

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.