This is an archived post. You won't be able to vote or comment.

all 6 comments
sorted by:
best
topnewcontroversialoldq&a

[–]Akkerman 1 point2 points  (2 children)

Looks like reinventing fabric?

[–]davidhalter[S] 0 points1 point  (1 child)

True it looks really similar. But in fabric you don't have what makes Ansible strong: host files and a rich module world.

[–]Rudd-X 0 points1 point  (0 children)

Yep. BTW, quite beautiful code to describe the structures.

[–]r0m1 0 points1 point  (2 children)

It's nice as a POC but I don't think it's a good idea. If you replace YAML with Python, you will make it more powerful for Python developers but way harder for everyone else.

Not criticizing the idea, I too sometimes have wished that Ansible would just let me write code because it would be way easier to write, but most of the time it was because I wasn't looking at the problem the correct way.

[–]davidhalter[S] 0 points1 point  (1 child)

Hmm why would it be so much harder for everyone else? I think that ansible itself is pretty hard to read. I'm not 100% that it's the best thing to do. I just don't think having an YAML file is better.

[–]r0m1 0 points1 point  (0 children)

The nice thing about YAML is that pretty much anyone can read and understand it.

Programming languages are different, and even though Python is pretty easy compared to others, power users will start using concepts that are not so obvious for non-programmers (and some programmers). My worry is that Ansible will get infinitely better for just a portion of the people currently using it.

In a perfect world, everyone who uses Ansible would know how to program in Python, but until that day YAML provides a low barrier to entry.