14 comments

[ 2.8 ms ] story [ 32.7 ms ] thread
Hello. I'm one of the maintainers, if you are interested in working on botoform, message me, my team is hiring.
See also: OpenStack Heat, which is not the same because it's a restful api, but I believe it's AWS-compatible.
Can Heat be decoupled from the whole OpenStack infrastructure? I wish there was something fully-compatible with CloudFormation that can be run locally, but if I have to rebuild the entire OpenStack infrastructure to accomplish that, it's gonna be an overkill.
How does this compare to Terraform, which allows you to manage infrastructure other than AWS (GCE, DO, bare metal, etc.)?
Its written in Python and uses YAML instead of whatever config markup Terraform uses.

My goal is to keep Botoform focused only on AWS and make it more intuitive and enjoyable to use then something like cloud formation.

Also I hope the project becomes an example of how to use Boto3.

This actually is great. Although Terraform is nice, it's too focused on supporting everything instead of doing one thing and doing it great.
Cool project! What advantages does this have over using CloudFormation?

I think that's the #1 question people coming to the repo will have, so maybe the repo README should provide a detailed comparison :)

Thank you for the advice. I'll do that right away.
Include terraform if possible.

And I use github.com/lucidsoftware/cumulus .

(comment deleted)