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

Hmm, just found the pulumi-command provider, that could be an option.

I’ll give it a try, even though it is marked as preview.

But I am open for further suggestions :slightly_smiling_face:

Yeah we have a build process that zips the artifact (lambda go binary) and puts it in artifactory. Our infra build then pulls it down right before an infra deployment and reference that zip as part of an infra release. 

So in your case use code build to publish an artifact to s3. Then point your infra to the new release 

<@U04AMPDFBBL> Ok, so you do compile the lambdas in a different step before issuing the pulumi up. I guess that may be a better solution that with the command-provider to do the go compile lambdas/cmd/…

Yes always. That way I can run all my tests separately keeping my app code separate from my infra 

If my tests or compilation fails then it never makes it to my infra 

You can use <https://pkg.go.dev/embed>
Sorry for late answer!