SST Console Not Tracking Ion Deployments
Hello SST team,
- I've noticed that the SST Ion console is not tracking deployments to AWS at all.
- To alleviate this, I hit the 'rescan' button under 'Manage Workspace' > 'Accounts' > 'Rescan' (I had my account connected for use with earlier version of SST). I've mostly been using
bunx sstinstead ofsst... howeversst versionyields - Despite doing this, all my previous deployments show up as 'project_name/stage_name'... however, I am never able to see their resources. All I see is 'Waiting for resources…' perpetually.
- I have no way to track my deployments to AWS any other way since SST Ion doesn't rely on CloudFormation (as it used to). What if I want to remove my deployments (repo's deleted because it was a 'test' deployment)?
Cheers, PG
I've seen this before but can you try doing a deploy after you've rescanned your account?
It's quite spotty. No clue what fixed it. But I just deleted my previous projects and created a new SST project and deployed it and it somehow didn't suffer from the same issue?
Perhaps it's me having pressed the 'rescan' button after a long period of inactivity on SST (last time I had used it was 6 months ago or more... before Ion was big)
Yeah it could be. So are the deployments showing up?
I have this issue as well.
I have connected my account to the console, it finds the project and associated stages, however if I click on a stage it just hangs on "Waiting for resources…"
Yeah it could be. So are the deployments showing up?
No, not always. Also seeing something similar as the above user every once in a while. I have to fiddle around with it (removing, redeploying, forcing SST to re-scan my AWS account etc.) to get it to work (that is... if IT ends up working at all). This is all fine in 'dev' but it's not OK when it's also impacting me when deploying to 'production' stage.
We pushed out some updates this past week. Can you try syncing your AWS accounts again?
This has resolved for me.