Does SST provide any convenience method/command for invoking local functions directly. I understand and see many examples of using integrated services to trigger the local function via the debug stack (APIGW, SQS, all the other things). But I’m curious if there is a more convenient way when working on initial iterations of a function without any triggers yet. I know I can invoke the stub directly from AWS console or using AWS CLI, but does SST provide any type of local invoke command? I couldn’t find anything in the docs, but figured I would ask here.

@Frank just released a local ui recently checkout the last release

@Austin update to v0.52.0 and use the

--console

flag

Here’s the announcement thread in #general: https://serverless-stack.slack.com/archives/C01JVDJQU2C/p1637094338302200

thats really cool, I created a little stack I use for this, ill give feedback if any features are missing. Your guy's sounds much more pleasant to use.

Awesome, thanks everyone! Perfect timing haha

I think mainly the only features missing to totally replace my mini stack would be to introduce: • Functions that are just invoked directly (standalone). • The ability to send payloads (body on API or Payload on invoke or Eventbridge/SNS/SQS, etc). This feature may exist on some of these, but I haven't seen it.

Thanks @Derek Kershner! Putting them down. To the second point, SNS/SQS already supported, EventBridge coming soon.

ok, I hadnt tried SNS yet, but that is helpful to me. Thank you.

Personally I set the CRON memory to 128MB locally, and just let them run. But now you mentioned it, I think we can make this an option to

sst start

.

I’ll second @Derek Kershner and say it would be awesome to see sst.Function construct explicitly in this tool and allow invoking it directly. I am not using the Cron construct as I’m using an EventBridge rule to schedule a Step Functions state machine execution, which leverages the sst.Function. Would love to be able to invoke the function locally directly without needing to go through EventBridge or Step Functions.

@Austin noted!

Personally I set the CRON memory to 128MB locally, and just let them run. But now you mentioned it, I think we can make this an option to 

sst start

.

@Frank, I worry about if you had 10 developers and a downstream rate limit or something, because the local stack stays deployed and will run forever (without specifically removing it).

This is great feedback! Thanks all!