I updated the top 2 lines to look the ones in the main go-aws-shim repo
HANDLER ?= handler
PACKAGE ?= $(HANDLER)
PACKAGE ?= $(HANDLER)
Although that seems to have broke the building process.
early 2018
i can't think of where else i could look to find the file?
in Windows, can I use eawsy/aws-lambda-go-shim?
is bash the only option?
Hi @superbmilkyway_twitter , for windows you have to have Docker installed and also Make for windows. After what you proceed as described in the README to deploy your first function. Basically downloading the provided Makefile, creating a hello world handle and executing
make .
we update the shim with the latest available Go stable version. For now it's Go 1.9.2. So by using the provided Docker image you're tied to the provided version. But you are free to build a custom image with the go version you want. For this version of shim we rely on Go 1.8+ plugin feature. And some bugs have been fixed with Go 1.9 so, IMHO use the version we provide :smile:
Thank you again :)
rather than the event
On that note... is there a known work around for
Unable to import module 'handler': plugin.Open: plugin was built with a different version of package errors
The issue appears to be because I'm vendoring the dependencies and the package building pulls the latest version of the
Dockerfile
Hey guys, I am looking at the supported events list (https://github.com/eawsy/aws-lambda-go-event) and I don't see SQS. Are there limitations to sending messages with SQS with the shim?
I somehow cannot get gzip compression working using https://github.com/NYTimes/gziphandler
I used your binary example and set the []string{"gzip"} content type. Binary Support is also enabled on API Gateway. Any idea what might be wrong?
I used your binary example and set the []string{"gzip"} content type. Binary Support is also enabled on API Gateway. Any idea what might be wrong?
@mzd555 In general, as the shim relies on Go 1.8+ plugins, you can leverage a
main function to call your handler. This main function is removed automatically when compiling the handler for Lambda. Otherwise you can write unit tests or take a look at the "integration tests" of the shim. If you only target API Gateway, I advocate using https://github.com/eawsy/aws-lambda-go-net which allows you to leverage existing Go HTTP API and/or framework so that you do not have to do anything special related to Lambda.
In general you dont have to look in the python side to know how it works in go. The promise of the shim is it behaves exactly like pure native go. If not, it's a bug :smile: So for the lifecycle you should find any good doc on db connection and go init function and apply it to your Lambda through the shim :wink:
the /internal import appears not to be a problem in the supported version