plugins VS Previous Serverless Version 0.5.x

Plugins

You can ease your pain by using plugins. Some are already built for the most common problems (check them out in the official Serverless Plugins Github repo), but there are always some project-specific issues that plugins can help you resolve. Fortunately, writing a plugin for the Serverless Framework is easier than you might think.

Before getting started, you need to install the plugin. This is hosted on the Serverless Plugins registry, so you can install this via the plugin install command which is introduced since v1.22.0.

service: functions useDotenv: true provider: name: openwhisk functions: autoai: handler: handler.autoai parameters: api_key: ${env:api_key} events: - http: POST /autoai # extend the framework using plugins listed here: # https://github.com/serverless/plugins plugins: - serverless-openwhisk - serverless-dotenv-plugin

The plugins are built by the Serverless community. Anyone can create a plugin. The Serverless Framework company lists plugins, but only a subset are "approved." This means we should be cognizant of what we are using.

Github | Website

i deployed a lambda and http api gateway using a serverless.com (sls) template as a start. I get the following error when it processes a specific request:

Have you tried serverless.com ? It lets you have infrastructure as code.

- With Lambda, you manage creating and building the container yourself, as well as updating the Lambda function code. There are tools out there such as sst or serverless.com which help streamline this.

If you'd like to use Lambda, usually you need to engineer FOR it, from day one, you don't (often) get to choose some other framework and shoehorn it into Lambda and Serverless. There's some great frameworks to help deploy code into Lambda easily and create REST endpoints for things, one such frameworks is serverless.com that helps easily deploy to it, but it lacks a framework for doing REST that also supports local emulation (as easily). For that, I recommend a framework by AWS called Chalice. This is an amazing REST framework that runs a proxy that works locally and deploys exactly the same on Lambda, it is Python however.

I use serverless.com for AWS stuff.

After knocking out a README with a set of goals and a list of TODOs to check off as I made progress, I spent about 10 hours over a weekend trying to get something to work. I used serverless for making Lambda easier, Github Actions for the deploy pipeline and store my credentials; and sadly I rolled my own access_token refresh logic because I couldn't find a helper that just did that for me! wtf!?

Does everyone who uses Workers just use wrangler cli and the cloudflare console UI for everything or is anyone using other tools like serverless framework (https://serverless.com) instead? Looks like they added some support for cloudflare but haven't tried it yet.