How do you deal with that cannot delete export because it is in use thing again

Last time that happened, I had to manually trace together the stack dependency tree, delete each stack manually (including clearing the S3 buckets for each one…), leaf first

That's what I'm doing which is ok because it's in dev...but what happens when this happens in prod

yeah…that experience taught me to never delete anything 😬

I hate cloudformation 😢

I’m paying for empty VPCs all over the place right now because of this, taking baby steps to remove them bit by bit

Yeah it's like if you don't get everything right all the time you're screwed

Removing all and deploy all again.

I think sst can help diagnose this better than the confusing error you get from cdk

I would like to.

@Frank told me to just manually add the export to my code, then deploy.. so since the export is there, it won’t delete it. then after deploy, remove that manual export and deploy again

Oh boy we're not the only ones then. We get this issue whenever we want to change a bucket name, (trashing an old bucket from CDK for a new one).

@thdxr I gave this some thoughts. I think there might be a way for SST to detect this early. Imagine 2 stacks, stackA exports

tableArn

and stackB imports it. And now we remove the reference to

tableArn

in stackB, and stackA’s export will automatically be removed.

yeah

So what we could do is, on `sst deploy`: 1. get currently deployed exports for each stacks, and find out which stacks are currently importing each 2. check if exports have changed 3. if exports are changed and will cause an issue, we automatically add the export 4. deploy