serverless-go-plugin
serverless-go-plugin copied to clipboard
⚡️ Serverless Framework plugin that compiles Go functions on the fly. Sponsored by https://cloudash.dev
Currently the docs still showing support for package includes, but that is no longer the supported format and should use package patterns instead any way to move to supporting this?...
Hello, I was wondering how this works in regards to cross compile support for libraries that link directly to C code? I know in the `serverless-python-requirments` plugin they allow for...
When defining a serverless.yml file with a top level package element, the includes are not respected unless they are included in the specific function definition. Without this plugin, the includes...
Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6. Commits 7efb22a 1.2.6 ef88b93 security notice for additional prototype pollution issue c2b9819 isConstructorOrProto adapted from PR bc8ecee test from prototype pollution PR See full...
Support path resolver for baseDir, so that we can use handler's dirname as baseDir.
Encounter error below when I am trying to include a binary into a function. Or did i miss out something Error: ``` ✖ Stack failed to deploy (125s) Environment: linux,...
If there were package.include specified for a function that used a bootstrapped runtime the includes would simply be ignored. This PR will add the includes to the zip-file and ensure...
Bumps [json5](https://github.com/json5/json5) from 2.1.2 to 2.2.3. Release notes Sourced from json5's releases. v2.2.3 Fix: [email protected] is now the 'latest' release according to npm instead of v1.0.2. (#299) v2.2.2 Fix: Properties...
Hello. I'm trying to update the runtime for serverless function from go.1x to provided.al2 using the serverless-go-plugin. I have the following configuration which deploys fine, but during runtime I get:...
Due to the `go1.x` runtime deprecation, I am trying to use the custom runtime `provided.al2`. However, the endpoint now gives the error "**Endpoint request timed out**" after deployment. Any advice...