This message was deleted.

sparse-intern-71089

09/15/2020, 9:15 PM

This message was deleted.

some-flower-64874

09/16/2020, 7:06 AM

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 -> test -> stage -> prod ) without a rebuild. That though is full of my assumptions about the way the world should work...

millions-judge-24978

09/16/2020, 3:10 PM

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

millions-judge-24978

09/16/2020, 3:11 PM

I ended up just doing something like this

Copy code

const build: pulumi.Input<void> = (async () => {
      await execa.command('make lambda-zip', { cwd: '..' })
    })()

where that make target does the

go build

some-flower-64874

09/17/2020, 7:21 AM

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.

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.