We are suspecting that SST/CDK is force updating t...
# sstd
Dan Van Brunt
11/10/2021, 2:07 PMWe are suspecting that SST/CDK is force updating the CF Distro on each deploy even when nothing should have changed. Since this process adds 6mins+ to each deploy we’re interested in how best prove that something is indeed changing for the distro and causing the update to it. Is there something we can use like sst diff or cdk diff ?
t
thdxr
11/10/2021, 2:08 PMThe way I've observed it work for myself is once the stack is built, if the resulting bundle is the exact same it will not deploy any updates to s3 which won't trigger the invalidations
thdxr
11/10/2021, 2:08 PMWhat you can do is before running an sst deploy you can do an
sst diffd
Dan Van Brunt
11/10/2021, 2:09 PMinvalidations shouldn’t trigger the CF resource to update though?
t
thdxr
11/10/2021, 2:10 PMThe new files get uploaded to a new folder in s3 and cf distro must be repointed at the new folder
d
David Martin
11/10/2021, 6:20 PMI moved my ‘www’ nextjs project into a different SST deployment because of the long delay. Here’s a screenshot of my monorepo projects, www has its own sst.json