3 ms·
Why are you bringing down the RDS stack to make cloudformation udpates? Can you share an example of something that makes you need to do this over and over again
by carlsborg 6y ago
Why are you bringing down the RDS stack to make cloudformation udpates? Can you share an example of something that makes you need to do this over and over again?
- davedx 6y agoI'm creating a database with parameters, roles, backup buckets and so on. Usually each time I run the stack I either get a template error, or the stack partly runs then hits some other error. Then the stack rolls back, and re-running it will fail because it's in rolled_back state. So then I need to delete the whole thing and start again. When I can simply re-run and update the stack without deleting it I do (for example if I just change a property of one of the resources). But I spend a lot of time with stacks that are in broken states for various reasons.
- acdha 6y agoI share this pain - it’s a major reason why we switched to Terraform, along with not having to wait 6-12 months for support for new AWS features - but I would recommend using CDK to generate your CF stacks. The cfn-python-lint tool was helpful for catching many things without a 20 minute delay but CDK goes even further on the boilerplate reduction and a real programming language beats YAML in every way.
- carlsborg 6y agoMaybe changesets would be useful here. It’s like terraform plan but better because it’s aws native. $aws cloudformation deploy. .. —no-execute-changes etc https://docs.aws.amazon.com/cli/latest/reference/cloudformation/deploy/index.html https://docs.aws.amazon.com/cli/latest/reference/cloudformat...