📢 Update

In v0.52.0, we added SST Console — a web based UI that shows you all the constructs in your app, and you can manually trigger them. This allows you to live debug a Cron job without needing to wait for it to get invoked; debug a Queue consumer directly without needing to invoking the API that sends a message to the queue first; etc. We kept the features to the minimum for this early version. Let us know what features you’d like to see. To give it a try, run

npm run start -- --console

or

yarn start --console

I’ll also add that I think it does a better job of highlighting if there are any errors in your app and if there are any infrastructure changes that need to be deployed.

WOW. this is so cool. much needed feature. Q, I just ran it on mine, does it suppose to show all the constructs, it's only listing Api and dynamo tables only?

I am noticing that my EventBus targets are not showing I would suggest if possible to add support for EventBus and SNS

This looks like a great addition. One thing I've noticed that if the stage is appended to the API URL, the browser console isn't aware of it. e.g. clicking on one of the routes labelled

/somepath/add

when the stage is my-stage just bring up

my-stage/somepath/add

but my-stage is missing so the api call fails unless you manually adjust in the browser. I guess this is only really useful for GET as it opens in the browser but being able to copy/paste the accurate URL for curl or Postman would be handy

@Sione yeah currently Console only shows SST constructs.

Neat, looking forward to checking this out!

@Ross Coundon gotcha.. is this for

ApiGatewayV1Api

?

No, it's the HTTP API

And you are setting the stage name in the custom domain base path?

We do it via an HttpStage e.g.

new HttpStage(this, 'Stage', {
      httpApi: api.httpApi,
      stageName,
      autoDeploy: true,
    });

Got it! Will give it a try - https://github.com/serverless-stack/serverless-stack/issues/1043

cool

@Frank so SST functions should be shown, right? SST functions not showings on mine.

Are these standalone functions not tied to other SST constructs?

Oh this sounds great! Thanks @Frank

@Frank Yes, they are all standalone SST functions.

@Sione got it! Just curious, are they being used by non-SST constructs?

Yah they used as consumers for cdk eventbridge, kinesis stream and tasks in step functions.

@Sione Got it! Noted!

@Branko Gvoka ;)

@Ross Coundon following up on the stage name issue, do you have

createDefaultStage: false

set in ur

sst.Api

?

Hi @Frank - yes we do

@Ross Coundon should be fixed in v0.53.0

Great, thank you

I am seeing the same thing as @Sione, sst functions are not showing.

this is interesting! though I’m not sure what I should use it for. I can’t actually fire off crons because no Lambda functions are listed. all I can do is copy URLs from my resources. (I can’t invoke API calls since it requires auth) you know what would be REALLY awesome in this UI? instead of the raw text REQUEST/RESPONSE lines, actual calls that you can expand to see the full request payload & response payload

@Sam Hulick noted the request/response payload

@Frank my mistake, I must’ve missed it! thanks 🙂

@Frank @Jay I cannot see the Queue that I defined in my stack definition. Am I doing something wrong? 🤔 My Stack | The Console

@Frank have a look at this when you get a chance!

hey @Ömer Toraman, it seems you are using the

sqs.Queue

. Currently only `sst.Queue`s show up in the Console.

Oh I see, so only

sst

Constructs will show up?

Yeah at the moment. Most likely supporting CDK constructs as well down the road.