Interesting Uses of Ansible's ternary filter

Re:Interesting Uses of Ansible's ternary filter by zufallsheld on Thursday February 22, 2024 @10:03AM (#39468104)

As a counter anecdote I can tell you that all of the ops-people I worked with, they gladly switched from Puppet and Chef to Ansible, specifically because it was less programming and more shell-like.

Not that this is good or bad, but I think that's why Ansible took off with the traditional operations-teams.

[ Parent | on HN ]

Re:Interesting Uses of Ansible's ternary filter by jauntywundrkind on Thursday February 22, 2024 @12:50PM (#39470588)

More shell like, and more normative. There's a given form & shape in Ansible; playbooks resemble each other.

You don't get that with programming languages. People do all kinds of shit with programming languages. There's tons of good ways to tackle a problem. And exponentially many more bad ways to tackle a problem.

Having a given repeated form makes interpreting & understanding Ansible far easier than the alternatives.

[ Parent | on HN ]