I really have to practice more with updating stack...
# helpa
Adrian Schweizer
12/03/2021, 11:03 PMI really have to practice more with updating stacks...it almost always fails for some reason (e.g. when I change some dynamodb config), then I delete the tables through amazon gui, try again and it seems even worse than before, usually resulting in a stack that sits forever in delete pending
Adrian Schweizer
12/03/2021, 11:04 PMis there some handy guide with a few scenarios that tells you what to do when you updated different things in your stacks?
d
Devin
12/04/2021, 2:10 AMI have also experienced this problem. Not that this helps you. Just wanted to let you know you're not alone!
f
Frank
12/04/2021, 3:52 AM
@Adrian Schweizer if you have a specific scenario, ie. what config you changed and what CFN error do you get. I can see if it’s something specific to ur architecture, or just CFN being CFN 🤷‍♂️
a
Adrian Schweizer
12/05/2021, 1:09 AMYeah, I'll take some notes next time. I have a feeling it's probably the latter.
ö
Ă–mer Toraman
12/05/2021, 3:36 AMI guess that is because the changes you made require replacement for the resources, i.e., removal of the resource, and creation of a new resource.
I also come across with this, with DynamoDB, say you change the primary key configuration, then I guess the easiest way would be to change the table name.
a
Adrian Schweizer
12/05/2021, 8:31 PMyeah, I just had this, I changed the name of a global seconday index, then tried to redeploy (it detected a change), but redeploy failed, with error
Cannot perform more than one GSI creation or deletion in a single updateAdrian Schweizer
12/05/2021, 8:32 PMso i tried npx sst remove --stack=storage to remove the whole stack, and now it's deletion pending and won't stop
Adrian Schweizer
12/05/2021, 8:33 PMso I guess the way to go would be to first add GSI with the new name, redeploy, then remove GSI with old name?
ö
Ă–mer Toraman
12/05/2021, 8:45 PMYeah, or vice versa. But I guess a guide on updating stacks is really important, because what if you had this change in a production environment/stage.
a
Adrian Schweizer
12/05/2021, 9:31 PMyeah, I have no idea and am actually quite scared to go live with my app
ö
Ă–mer Toraman
12/05/2021, 9:32 PMlol
Ă–mer Toraman
12/05/2021, 9:32 PMI guess you need to first create a changeset and see what resources will create-deleted-modified
Ă–mer Toraman
12/05/2021, 9:33 PMand maybe chcek the resource policies for each property
Ă–mer Toraman
12/05/2021, 9:34 PMĂ–mer Toraman
12/05/2021, 9:35 PMand for each resource-property=>
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-template-resource-type-ref.html
a
Adrian Schweizer
12/05/2021, 11:15 PMhmmm, yeah, I gotta read up about cloudformation, I had very little exposure to it so far
Adrian Schweizer
12/05/2021, 11:15 PMthanks for the links
f
Frank
12/06/2021, 12:39 AM
Yeah, try to avoid manually changing/removing resources through AWS console directly. Whatever you change, CloudFormation isn’t aware of it. And when you deploy again, CloudFormation is likely to fail.
a
Adrian Schweizer
12/06/2021, 1:25 AMok, that's good to know as a general guideline