Ansible has started loudly deprecating the "with_items" construct in favour of the new "loop" construct. The old one is slatede to be removed.

Woe be anyone who needs to run ansible-playbook on both old distros and new, and needs to have the same playbooks work on both.

At least it looks like a long deprecation period, but this kind of thing makes me wonder if I should look at some other tool instead.

I like that Ansible doesn't require an agent running on the target host. Some of my use cases pretty much rely on that.

It's too bad that I'm not comfortable with Haskell, or I'd dive into Propellor.

@liw my feeling re: ansible at this point is pretty much _run away_, but then also there aren't many things in ansible's space that i don't feel that way about.

at least it's not chef.

@liw the main problems I see with propellor is that (1) it's closely entangled with git, and (2) builds itself on the target, requiring all sort of GHC stuff there.

Apart from that, it's pretty decent. It's certainly a lot faster than Ansible. I'd guess a hundred times faster or so.

So if it were building a single binary on the host and then copied that to wherever it's supposed to run via scp and executes it, it would be fine.

@juliank @liw there's a patch for propellor to send a precompiled binary, but it's been stalled since 2017

It only needs testing of a few edge cases.

I'm too lazy to test it myself..

Could old hosts use the more recent Python package (e.g. in a virtual environment)?

Sign in to participate in the conversation
Social Nasqueron

Nasqueron is a budding community of creative people, writers, developers and thinkers. We focus on free culture, ethics and to be a positive change. We share values like respect, justice and equity.