💥 Breaking Change
AppSyncApi: if you are using the AppSyncApi
construct, existing resolvers need to be removed, and then added back. To add a bit of background, Resolvers were previously created within a DataSource's construct scope. When you try to update the DataSource for the resolver, deployment will fail with the CloudFormation error Only one resolver is allowed per field
. By creating the Resolvers within the AppSyncApi's construct scope, this error will not happen. But to make this change, existing resolvers need to be removed; and then add them back in the next deployment. Read more about the issue here - #417
🚀 Enhancement
- #427 StaticSite: do not run build command on sst remove (@fwang)
- #430 sst start: add
--increase-timeout
flag to allow testing with breakpoints (@fwang) - #429 sst start: expose the app and the stack constructs in the debug stack (@fwang)
🐛 Bug Fix
- #418 AppSyncApi: create resolver from the api not datasource (@mmccall10)
- #425 StaticSite: create certificate in us-east-1 region (@fwang)
Contributors:
- Mike McCall (@mmccall10)
Update using:
$ npm install --save --save-exact @serverless-stack/cli@0.26.0 @serverless-stack/resources@0.26.0