Announcement time! + a surprise!
After having v1 in beta for a month, SST v1 is finally out! We really appreciate all the folks that tried it out and gave us their feedback.
Moving forward we'll stop adding updates to v0. But we are here, in case anybody needs help migrating to v1. v1 gives us a good base to build on and we've got some exciting features lined up!
A conference??
With SST v1, we are entering into a new phase of development. We wanted to do something special to commemorate the v1 launch. So we are putting together a virtual event for it!
SST 1.0 Conf is a free virtual event happening on May 17th at 9am PDT. We've got a couple of folks from Comcast, The LEGO Group, Shell, and Analog Devices that'll be speaking. A couple of us from the SST team will be doing workshops as well. If you'd like to give a talk, here's a little form we'd like you to fill out. All the talks will be super short, around 10 minutes: https://forms.gle/KTdbCLUy5oNwos2m7
We'll share more details about the conference in a couple of days but we wanted to give you all a heads up before we share it with the world. We want to use this event as a way to bring our community together and to share what we've all learnt!
Cue the excitement! 🎉
Migrating to v1
Follow the steps in the migration guide to update.
The problems we are trying to address
There are a couple of common issues we've observed with people using SST:
- How do I know a prop I'm configuring is a CDK prop vs a SST prop?
- And related, do I need to read CDK docs and import CDK dependencies?
- How to configure underlying CDK constructs?
- How to access the CDK constructs created internally inside an SST construct?
- Lack of warnings when specifying invalid construct props
- Having to constantly visit the SST docs
The fix
We restructured the constructs to address these issues. You can read more about the details in the migration guide: https://docs.serverless-stack.com/constructs/v0/migration#goals
Most of the changes are reorganizing and renaming construct properties, attributes, and adding TS Docs. The underlying resources (ie. the CloudFormation template) are mostly not impacted. There should be zero downtime during the upgrade.