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

That's an interesting question - from where I sit Pulumi is the wrong place to call `go build` since I would expect build/package to be a step or two before and to be able to use Pulumi to deploy the _same_ package to multiple environments (e.g. dev -&gt; test -&gt; stage -&gt; prod ) without a rebuild.
That though is full of my assumptions about the way the world should work...

I think the line gets blurred often, for example pulumi will happily build docker images for you and it can provide a really nice UX

I ended up just doing something like this
```    const build: pulumi.Input&lt;void&gt; = (async () =&gt; {
      await execa.command('make lambda-zip', { cwd: '..' })
    })()```
where that make target does the `go build`

The challenge with having _pulumi_ build the images for you is that one wants to deploy the same image to all environments - if its built each time then its not the same image. There are counter arguments - and I agree its neat.