I saw that cfnrain is a fork of the archived rain CLI. What does it do differently from the AWS CLI or SAM, and what should existing rain users know about switching?
What's the appeal of cfnrain for CloudFormation deploys?
Answers
The deploy experience is the big draw. It shows a readable change set, asks for confirmation, and displays progress as the stack updates. When something fails, it can surface the underlying error even if it comes from a nested stack.
That's useful if you're tired of digging through CloudFormation output to figure out what went wrong.
Reply to this answer
SAM isn't quite a drop-in substitute. It's a framework aimed at serverless applications, with its own abstractions and project structure. Rain is a general-purpose client for working with CloudFormation directly, plus some template helpers.
Reply to this answer
For existing users, cfnrain v1.25.1 is the original rain code under a new name. Templates, directives, config files, and artifact buckets are meant to work as before.
That doesn't promise permanent compatibility. Dependency updates are planned, and later changes could break compatibility where there's a usability reason to do so.
Reply to this answer
It's not only about deploy output. Rain can format templates and package files, and its !Rain::Embed directive lets you keep code in a separate file while embedding it in the template at deploy time. That's a handy feature to check for if you're comparing tools.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_p4!nimbrel.8:
So the choice depends partly on whether you want those serverless framework features or just a nicer way to work with CloudFormation.