Daniel Gato
04/12/2022, 11:59 AMdeploy stack: run cdk deploy
deploy stack: poll stack status
deploy stack: poll stack status: {
StackStatus: 'UPDATE_COMPLETE',
LastUpdatedTime: 2022-04-12T08:11:52.538Z
}
deploy stack: poll stack status: unknown
deploy stack: poll stack status: {
StackStatus: 'UPDATE_COMPLETE',
LastUpdatedTime: 2022-04-12T08:11:52.538Z
}
deploy stack: poll stack status: unknown
....
We are 2 people experiencing the same on the same project
I already tried to delete .sst and .build just in case.
Edit: it worked for me but my colleague is still stuck on that for now 3hFrank
Daniel Gato
04/12/2022, 2:53 PMDaniel Gato
04/12/2022, 2:53 PMFrank
Daniel Gato
04/13/2022, 10:07 AMDaniel Gato
04/13/2022, 10:07 AMAthol Birtley
05/06/2022, 1:49 AMdeploy stack: poll stack status: unknown
deploy stack: poll stack status: {
StackStatus: 'UPDATE_COMPLETE',
LastUpdatedTime: 2022-05-05T09:08:09.531Z
}
When viewing the stack in Cloudformation Management Console, there are no change sets (but there is a ‘last executed changeset’ from 2022-05-05 T090809).
I will leave it running to see if eventually goes through, like Daniel did above, but thought you might like to know / might have an alternative suggestion.Athol Birtley
05/06/2022, 2:03 AMAthol Birtley
05/06/2022, 2:54 AMsst start
is very quick to get to “listening for requests…”Athol Birtley
05/06/2022, 4:41 AMap-southeast-2
region.
Also, I just tried creating a brand new SST project, with only 1 API endpoint, and that was also incredibly slow to sst start
. Took at least 15 minutes for the debug stack to even appear in AWS (but it then created quite quickly), and then a further 12 minutes for the MyStack to appear in AWS (although again, once it appeared in completed quite quickly). It took 5 more minutes for SST to realise that the MyStack stack had finished creating though (perhaps due to an exponential backoff in polling?)Athol Birtley
05/06/2022, 5:37 AMAthol Birtley
05/06/2022, 5:54 AMREVIEW_IN_PROGRESS
state for a very long time (eg 25 minutes), before they actually start doing any work in Cloudformation. I’m not overly familiar with cloudformation / CDK, but is this because the change set is being created but not being manually ‘executed’ ?Athol Birtley
05/06/2022, 6:11 AMAthol Birtley
05/06/2022, 6:56 AMAthol Birtley
05/06/2022, 9:11 AMsst start
.Lewis Eccles
05/06/2022, 2:50 PMAthol Birtley
05/07/2022, 9:07 PM"resolutions"
parameter in my package.json to ensure SST was using it too. I also deleted .build and .sst. Running sst start
displayed a warning about mismatched versions of AWS CDK packages, which was expected. However, it did not solve the problem of take ages to detect whether the debug stack needed updating or not. (I stopped it after 10 minutes as I figured it wasn’t worth waiting any longer.)
Then, I reverted my project to use SST v0.69.3 (what I had been using previously, when things were working fine), and reverted CDK to 2.15.0. Deleted .sst and .build again, and ran sst start
. Still no luck! (Minutes and minutes just to determine whether the debug stack was deployed (which it was)).
Then I gave up for the day, and tried again a day later. And what do you know - everything worked! Both SST 1.0.2 / CDK 2.20, and SST 0.69.3 / CDK 2.15.0 behaved as I was used to. It does take a minute or two to deploy when you switch from pre-1.0 to 1.0, but then if you stop sst start
and run it again, it is very quick to detect no changes to the stack and start listening for live lambda requests.
My thinking is that it was either a poor-connection issue at my end (that wasn’t resolved by upgrading CDK to 2.21.0), or that AWS Cloudfront in ap-southeast-2 was just having a really bad day. I’m leaning towards the latter, since I wasn’t having issues with anything else on the internet that day.
Hope this helps!Athol Birtley
05/11/2022, 5:51 AMAthol Birtley
05/11/2022, 10:58 PM