sst

🚀 Enhancement

• #1608 Function: Add architecture prop (@thdxr)
• #1601 Remove jest + eslint (@thdxr)

🐛 Bug Fix

• #1606 Cli: fix missing region in config error (@fwang)
• #1604 Cli: stack xxxx does not exist error on successful deploy (@fwang)
• #1596 Fix infinite rebuild loop (@omichowdhury)

Committers:

• Omi (@omichowdhury)
• Richard Simpson (@RichiCoder1)

Update using:

$ npx sst update v1.0.0-beta.9
$ yarn sst update v1.0.0-beta.9

🐛 Bug Fix

• #1605 Cli: fix missing region in config error (@fwang)
• #1603 Cli: stack xxxx does not exist error on successful deploy (@fwang)

Update using:

$ npx sst update 0.69.5
$ yarn sst update 0.69.5

🐛 Bug Fix

• #1597 Fix infinite rebuild loop (backport) (@omichowdhury)

📝 Documentation

• #1586 Update examples to latest versions (@Manitej66)

Committers

• Omi (@omichowdhury)

Update using:

$ npx sst update 0.69.4
$ yarn sst update 0.69.4

💥 v1 Beta is here

The problems we are trying to address

There are a couple of common issues we've observed with people using SST:

1. 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?
2. How to configure underlying CDK constructs?
3. How to access the CDK constructs created internally inside an SST construct?
4. Lack of warnings when specifying invalid construct props
5. 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.

Follow the steps in the migration guide to update.

Give it a try and let us know what you think! We are looking to launch v1 by the end of the month.

🚀 Enhancement

• #1497 sst-env: wait and poll while sst start is booting up (@alistairstead)
• #1570 Cli: support SSO and add the --profile option (@RichiCoder1)
• #1560 Cli: support absolute paths for the --outputs-file option (@drewfish)
• #1573 Cli: add error helper when cdk cli and constructs have different schema verions (@fwang)
• #1545 Console: add tooltips to icons in sidepanel (@Manitej66)

🐛 Bug Fix

• #1566 sst-env: fix cannot find environment when custom stack names are used (@hans-m-song)
• #1571 Fix "Cannot find app handler" when using custom file name in sst.json main entry (@fwang)
• #1559 Cli: handle previous exports not imported for auto export check (@fwang)

📝 Documentation

• #1542 Update Postgres example using RDS construct (@Manitej66)

Contributors

• Alistair Stead (@alistairstead)
• Drew Folta (@drewfish)
• Hans Song (@hans-m-song)
• Richard Simpson (@RichiCoder1)

Update using:

$ npx sst update 0.69.3
$ yarn sst update 0.69.3

🐛 Bug Fix

• #1548 Cli: fix invoking CDK cli issue on Windows (@fwang)
• #1547 Cli: fix sst cdk command exit code (@fwang)

Update using:

$ npx sst update 0.69.2
$ yarn sst update 0.69.2

Changes to StaticSite

We made some changes to how StaticSite, ReactStaticSite, and ViteStaticSite handle orphaned files during the deployment.

Prior to this release, on each deployment, files that were previously deployed but are no longer in the current deployment are NOT removed. This caused an issue where removed files/pages are still accessible after they have been removed from the site. Starting with this release, orphaned files will be removed by default.

You can control this behavior by setting purgeFiles to false.

new StaticSite(this, "Site", {
  path: "path/to/src",
  purgeFiles: false,
});

This affects the StaticSite, ReactStaticSite, and ViteStaticSite constructs.

🚀 Enhancement

• #1541 StaticSite: support removing old files (@fwang)
• #1533 StaticSite: replace environment in all html files (@fwang)

📝 Documentation

• #1535 Auth: Fix documentation typo (@philipliberato)
• #1529 Update Datadog example to CDK V2 (@Manitej66)
• #1512 Added Thundra example (@Manitej66)

Contributors

• Philip Liberato (@philipliberato)

Update using:

$ npx sst update 0.69.1
$ yarn sst update 0.69.1

🚀 Enhancement

• #1514 Functional Stacks (@thdxr)

📝 Documentation

• #1501 Update architecture.md (@wmbond)

Committers

• Bill Bond (@wmbond)

Update using:

$ npx sst update 0.69.0
$ yarn sst update 0.69.0

🐛 Bug Fix

• #1508 Fix: do not use dynamic file migrator in production (@thdxr)

Update using:

$ npx sst update 0.68.1
$ yarn sst update 0.68.1

🚀 Enhancement

• #1500 Update CDK to 2.15.0 (@fwang)

🐛 Bug Fix

• #1498 Console: fix KinesisStream consumers not showing in functions tab (@Manitej66)

📝 Documentation

• #1476 Add example for Angular (@Manitej66)

Update using:

$ npx sst update 0.68.0
$ yarn sst update 0.68.0

🚀 Enhancement

• #1483 Better packaging for @serverless-stack/node (@thdxr)
• #1459 Console: copy signed url of object instead of s3 url (@Manitej66)

🐛 Bug Fix

• #1470 Console: fix undefined error stack trace crash (@fwang)

📝 Documentation

• #1460 Console: fix dynamoDB copy (@Manitej66)

🆕 SST Console / API

This update features a new API Explorer that lets you to make HTTP requests to your sst.Api and sst.ApiGatewayV1Api. Easily set headers, query params and body to make a request against any of your routes and view the function logs as well as the response.

🚀 Enhancement

• #1451 Explorer: API (@thdxr)
• #1454 fixed showing the loading sign while creating new folder (@Manitej66)
• #1444 Clean up dependencies (@thdxr)

📝 Documentation

• #1442 Fix lambda transpiling issue in mongodb example (@Manitej66)

Update using:

$ npx sst update 0.67.0
$ yarn sst update 0.67.0

🐛 Bug Fix

• #1449 Function: do not set esbuild "external" without "bundle" is disabled (@fwang)

Update using:

$ npx sst update 0.66.3
$ yarn sst update 0.66.3

🚀 Enhancement

• #1448 sst start: add Lambda contexts required by Lambda power tool logger (@fwang)

🐛 Bug Fix

• #1439 sst start: need to hit ctrl-c twice to exit the process (@danieloi)

📝 Documentation

• #1435 Typo in auth.md (@julbrs)

Contributors

• Julien Bras (@julbrs)
• Mayowa Daniel (@danieloi)

Update using:

$ npx sst update 0.66.2
$ yarn sst update 0.66.2

🐛 Bug Fix

• #1443 sst start: setting NODE_OPTIONS in Lambda environment causes VSCode breakpoint not working (@fwang)
• #1441 sst start: fix large payload IllegalLocationConstraintException error in new regions (@fwang)

Update using:

$ npx sst update 0.66.1
$ yarn sst update 0.66.1

🆕 SST Console / DynamoDB

This update features a new DynamoDB Explorer that lets you query your sst.Table directly from the web console. You can scan the table, query specific keys and create/edit items.

🚀 Enhancement

• #1418 Explorer: Dynamo Console (@thdxr)
• #1413 Allow overriding s3 bucket and function props in debug stack (@fwang)
• #1431 sst start: show descriptive error message when remote Lambda timed out (@fwang)
• #1430 sst start: show descriptive message for "Unable to find function" (@fwang)
• #1412 Auth: import existing UserPool (@fwang)

🐛 Bug Fix

• #1420 RDS: fixed 0 showing as (@Manitej66)
• #1415 sst start: add trace to Python bootstrap.py error reporting (@estyrke)

📝 Documentation

• #1433 Fixed typo in docs (@ackinc)
• #1419 Update schema compiling for middy example (@Manitej66)

Committers:

• Anirudh Nimmagadda (@ackinc)
• Emil Styrke (@estyrke)

🐛 Bug Fix

• #1414 Copy migration to temp file to bust cache (@thdxr)
• #1411 Check for instanceof DebugStack is not reliable inside DebugApp (@fwang)

📝 Documentation

• #1406 Editing docs for the debug stack (@jayair)

Update using:

$ npx sst update 0.65.6
$ yarn sst update 0.65.6

🐛 Bug Fix

• #1401 RDS: Fix running migrations on windows (@thdxr)
• #1396 Prevent loading jsdom, which mocks fetch/XHR (@hermanbanken)

Committers:

• Herman (@hermanbanken)

Update using:

$ npx sst update 0.65.5
$ yarn sst update 0.65.5

🚀 Enhancement

• #1355 Add AAAA records to support IPv6 for APIs and static sites (@pupeno)

🐛 Bug Fix

• #1389 RDS: fix attachPermission does not grant secretsmanager:GetSecretValue (@fwang)

📝 Documentation

• #1375 Update README instructions for typescript-monorepo example (@abirtley)

Contributors

• Pablo Fernández (@pupeno)
• @abirtley

Update using:

$ npx sst update 0.65.4
$ yarn sst update 0.65.4

Major changes to customizing DebugStack

When you run sst start, SST deploys a debug stack to setup Live Lambda Development environment. Prior to this release, you only could customize the debug stack after the stack had been created using the debugStack() callback. Starting with this release, you have full control over the DebugStack.

What do I need to do

1. Rename the callback from debugStack(app, stack, props) to debugApp(app);
2. Create DebugStack inside the debugApp callback;

  new sst.DebugStack(app, "debug-stack");

3. If you used to reference props.stage, change it to app.stage

Examples

If you were adding a custom tag like this:

export function debugStack(app, stack, props) {
  cdk.Tags.of(app).add("my-stage", props.stage);
}

Change it to:

export function debugApp(app) {
  new sst.DebugStack(app, "debug-stack");
  cdk.Tags.of(app).add("test", `${app.stage}-${app.region}`);
}

You can also customize the stack name and the synthesizer.

export function debugApp(app) {
  new sst.DebugStack(app, "debug-stack", {
    stackName: app.logicalPrefixedName("live-debug"),
    synthesizer: new cdk.DefaultStackSynthesizer({
      qualifier: 'randchars1234',
    }),
  });

  cdk.Tags.of(app).add("test", `${app.stage}-${app.region}`);
}

Read more about customizing the DebugStack.

🚀 Enhancement

• #1387 Allow customizing the debug stack (@fwang)

🐛 Bug Fix

• #1388 ApiGatewayV1Api: cannot set restApiName (@fwang)

Update using:

$ npx sst update 0.65.3
$ yarn sst update 0.65.3