Does 'blueprint' functionality have a place in Ansible?

It’s tentatively interesting to see Blueprint get a patch to support ansible playbook generation, and I believe because we are YAML based it would be simpler than the existing support for other CM tools.

That being said, I expect with all of these tools it generates pretty terribly organized content and misses the neccessary handlers. The golden image technique is fundamentally flawed, and it will manage things with services, packages, and files but miss the use of many resources in Ansible.

Also ansible does a lot more than CM, it can do multi-tier process orchestration and so on, and that wouldn’t be something blueprint could pick up.

I think it’s a starting point, not something I’d resist seeing in blueprint, but not something I’d ever really point people at to use either.

I think this is why you don’t hear too many people talking about Blueprint – it is a nice starting idea, but it is eventually going to break down and then you need to learn the tool, and it’s better to just start organizing things as you get going rather than trying to untar [sic] the ball of content it would auto-create.

–Michael

Also, I should point out, that project has not seen any commits in 3 months.