Frank

@garretcharp thanks for looking into this. Afaik the function's logical ID isn't the function name. Can you double check if the Lambda function is writing to `/aws/lambda/${logicalId}`? Can we catch...

Yeah, that might be the most reliable option.

@thdxr I've run into this issue as well. Seems like either pothos or the migrator function depressed the error.

Hey @emouragym, the `currentVersionOptions` field should be under `function`. So instead of this: ```js [route]: { function: "---handler", currentVersionOptions: { provisionedConcurrentExecutions: 5, }, } ``` try this: ```js [route]: {...

Hi @mendellerner, there might be a need down the road to pass additional stuff to the function. ie. parameters from the previous invocation: ```js await invokeUserFunction(fnCreate, { params: fnParams, oldParams:...

Hey @estyrke, the `sst test` command has been removed in SST v1. The command really just ran the `jest` command behind the scene without adding much value. In v1, you...

Hey @revmischa, I actually wasn't aware of this. So CDK doesn't rebuild an asset if it's already present inside `cdk.out`? I'm curious how do they know the asset doesn't need...

Hi @hermanbanken, I'm not able to reproduce this with the latest version. Here's the stack code I tried: ```js // stacks/MyStack.ts import * as sst from "@serverless-stack/resources"; class MyTable extends...

Hi @tobyspark, this is the correct behavior. If the PR stage and the production stage are in the same AWS account, the Route 53 record should not change. This is...

Hey @adsc, if you are using the SST Console, the `event` object is being printed to the console by default. Is that what you are looking for? For example: