Created example for creating an AWS Lambda in Go #553
Conversation
| build:: | ||
| GOOS=linux GOARCH=amd64 go build -o ./handler/handler ./handler/handler.go | ||
| zip -j ./handler/handler.zip ./handler/handler | ||
| go build -o go-lambda main.go |
There was a problem hiding this comment.
In the example I was referring to, the first step was to build go, but to be honest, I've never tried not building it.
EDIT: Just tried it on a different example, and seems like the changes to main.go don't persist unless I build it first.
There was a problem hiding this comment.
EDIT: Just tried it on a different example, and seems like the changes to main.go don't persist unless I build it first.
My understanding is that if you have the binary there, then it will be used, but if you don't, then we will effectively go run main.go. So what you are seeing might happen if you still have the binary there from a previous go build?
@EvanBoyle Is that right? And if so, is it documented yet?
There was a problem hiding this comment.
Just tested, and you're right that pulumi builds for us. I'll make this change with #554.
| @@ -0,0 +1,4 @@ | |||
| build:: | |||
There was a problem hiding this comment.
It may be inevitable - but having a Makefile here means this may not work well on Windows. There are some notes on doing this in a cross platform compatible way in https://github.com/aws/aws-lambda-go/blob/master/README.md#for-developers-on-windows.
| 1. Build the go files: | ||
|
|
||
| ```bash | ||
| make build |
There was a problem hiding this comment.
Btw - I’m hopeful that once we fix pulumi/pulumi#3593 we can automate this directly within the Pulumi program so that the separate step is not needed - but today I think it is so I like having this example as is until then.
|
Wow, nice! 🎉 |
Added an example for
aws-go-lambdafor #442.