is there any reason updating SST would cause a bun...
# help
s
is there any reason updating SST would cause a bunch of changes to various resources in my stack the next time I run
yarn start
? it’s updating my RDS, KMS key.. kinda random stuff
t
Likely from underlying cdk upgrade?
s
i’m not sure there was one this time around. I’m still at 1.132.0
I wish you could somehow do a diff after the fact. I’m really curious
f
Maybe try the
sst diff
command?
t
Sam want's to sst diff the stuff that's deployed with
sst start
so it's like an
sst start:diff
s
yeah, exactly
f
I see… what makes sense?
sst start:diff
or
sst start-diff
or
sst diff-start
or
sst diff --start
s
sst start --diff
?
maybe the same convention as the new
console
option
f
The
--console
and
--udp
are temporary beta flag that will be removed. I feel we are trying to diff, but using the
start
mode.
sst diff --start
makes a bit more sense to me.
@thdxr @Jay u guys want to vote on this?
t
Copy code
sst diff <mode>
Makes the most sense to me
j
Yeah I like the
sst diff
command as well. For
mode
@thdxr would it take
start
and any stage name?
t
yeah I think it already has a
--stage
option right
j
Oh right yeah. So adding the mode would mean that it checks the debug stack as well?
f
With mode, is it
sst diff start
or
sst diff --mode start?