Releases: getlift/lift
1.1.2
1.1.1
1.1.0
Lift v1.1 is all about SQS queues:
- new CLI commands to manage SQS queues
- more detailed documentation, including complete code examples
Queue commands
List failed messages, purge them or retry them using 3 new commands:
serverless <construct-name>:failed
serverless <construct-name>:failed:purge
serverless <construct-name>:failed:retry
Read more about Queue commands.
Queue examples
Never used SQS before? The new documentation includes a complete example to get you started, including:
- how to deploy a production-ready queue
- how to send messages to a queue
- how to process messages
1.0.0
🚀 Lift v1, here we go!
New "Construct" design
Lift v1 embraces the AWS CDK much further and introduces a construct-oriented design:
service: my-app
provider:
name: aws
functions:
# ...
plugins:
- serverless-lift
constructs:
# Lift constructs here
landing-page:
type: static-website
path: 'landing/dist'
avatars:
type: storage
Lift constructs are built on top of AWS CDK constructs, allowing us to take full advantage of the CDK and its included best practices.
Learn more about Lift constructs...
Beyond the syntax changes in serverless.yml
, there have been a few changes in some constructs:
Static website
Deployed static websites now automatically have recommended security headers. Better HTTP compression is also enabled by default (Brotli compression).
Security headers have been implemented using the new CloudFront Functions: they work perfectly for these kinds of use cases, and they deploy transparently without extra complexity (unlike Lambda@Edge).
The Lift documentation now also contains examples for deploying React and VueJS applications.
Webhook
Now that we have shifted to a construct-oriented design, each webhook construct gets its own event bus and API Gateway.
More constructs
More constructs are coming soon, stay tuned!
If you are looking for a specific construct, please open a discussion on GitHub!
0.9.2
0.9.1
0.9.0 - First public beta!
🎉 This is the first public beta of Lift!
Lift ships with 4 components that you can deploy in serverless.yml
:
Feel free to use these components and let us know what features you need next.
We are also more than happy to help! Open a GitHub discussion and we'll answer your questions.
You can also reach us on Twitter for help:
0.8.0
Release 0.8.0
Added features
- Queues component: The queues component is now available 🎉. It implements a production-ready asynchronous worker pattern using SQS, DLQ and your lambda worker. Feel free to participate in the Github discussion if you wanna take part in the component design implementation. You can start using the queues component in your
serverless.yml
service file with thequeues
root property. - Webhooks component: The webhooks component is now available 🎉. It implements a production-ready HTTP endpoint in order for 3rd party application to notify your app. Feel free to participate in the Github discussion if you wanna take part in the component design implementation. You can start using the webhooks component in your
serverless.yml
service file with thewebhooks
root property.
Please remember the project is still in beta and we do not recommend using the component features in production just yet as we might introduce breaking changes in the component internal design and API.
Coming soon
- 📖 Updated Github documentation of all 4 components and how to use them
- 📈 Monitoring and alerting functionalities for all 4 components with Cloudwatch
0.7.0
- Documentation: Added comparison to other serverless framework and benefits of using Lift
- Static Website component: Following discussion from last week, first implementation of the Static Website component is now available. Just add the
static-websites
property in yourserverless.yml
service file and play around with it ! It implements automatic cleaning of the Bucket before stack removal and display component information onserverless info
command. - File Storage component: The discussion regarding the File Storage component is open, feel free to give your feedback on the component interface and implementation