Hacker News new | ask | show | jobs
by substructure 1653 days ago
AWS CloudFormation had one of the worst user stories related to iteration time a few years ago.

The lack of feedback between the writing of the yaml file and validation of the structure/type/format was frustratingly slow. I would pay good money for better tooling in the Infrastructure as Code(IaC) space.

Waiting for the resources to update, fail with cryptic error messages, then slowly rollback only to then fail the rollback. Now in an invalid state, manual resource creation was required before the rollback would succeed.

The AWS cdk has improved this significantly. As a result the sun shines just a little bit brighter.

2 comments

Getting anything new working in CloudFormation is a great way to kill a day.
What exactly you'd want to see from such tooling that it improves your experience with AWS?