We almost had it in time for Christmas but a belated gift to our community 😄 We've been working hard the past month on the new SST Console. In this release we focused on lambda debugging and replaying invocations but we have a lot more coming over the new few weeks. The first line of code for this was written on December 12th - I'll be sharing a bit more about our frontend tech stack that enabled us to move so quickly, some interesting stuff in there

Looking forward to this!

This sounds awesome, looking forward to checking it out!

Dax had a busy December 😉

congratulations and thank you @thdxr, looks awesome!

this latest update is amazing! man.. the new web-based console rocks

Thanks Sam!

After upgrading, I see the URL to the SST Console as an output to

sst start

, but the console just says "Waiting for CLI..." What did I do wrong 🙂

Hm I'm using SSO as well but are you using that manual refresh script

I'm using aws-sso-util

Ok let me try that

I see

credential_process

set in my

~/.aws/config

file, if that's what you mean? It was auto populated with

aws-sso-util

using the

aws-sso-util configure

command:

[profile MY_PROFILE]
sso_start_url = <https://xxxxxxxx.awsapps.com/start>
sso_region = us-east-1
sso_account_name = MY Company
sso_account_id = XXXXXXXXXXXX
sso_role_name = AWSReadOnlyAccess
region = us-east-1
credential_process = aws-sso-util credential-process --profile MY_PROFILE
sso_auto_populated = true

gotcha I recreated your issue. IDK why I was avoiding aws-sso-util before, this credential process thing is clever

Yeah, I've enjoyed using the tool

Fixed your issue let me get a release out

I just upgraded to 0.55 and am seeing the same issue. Wondering if it's something I'm not doing correctly?

0.55.1?

Ahh, it was something I did wrong 🙂

hooray hope you enjoy 😄

It looks awesome so far!

Hi @Seth Geoghegan, what were you doing wrong? Mine is stuck in the Waiting for CLI state too.

I "upgraded" to the wrong version of SST, which was incorrectly typed in the release notes. Make sure you upgrade to 0.55.1

@Dillon Peterson are you using Safari by any chance?

I'm on 0.55.1 and still getting that unfortunately.

Ah yeah we should’ve mentioned this in the release notes. We don’t support Safari yet. It needs a local certificate that we’ll be adding in one of the coming releases.

Ok Chrome works!!!

👍

Alright thanks Jay!! Appreciate it. Great work guys, as always.

That’s awesome to hear!