So let me rant about it for a bit:
- Whatever that language is, it's not something invented on earth. I've given up on learning when to use quotes or how it wants its indentations and just copy&paste&destroy everything&restart when it doesn't work after 15 minutes.
- There are a few thousands tests in their test suite, which makes it quite a feat to introduce a bug that breaks what amounts to "passing variables to a subroutine": https://github.com/ansible/ansible/issues/17356. (2 hours today I won't get back). I seriously don't know any other software where I spend most of my time reading through github issues.
- It's a tool to manage hosts. Which would make me think that "reboot" shouldn't be a dirty word. But there's actually no function to do (a) ```/bin/sh reboot```, (b) wait for it to come back. First request I found is four years old: https://github.com/ansible/ansible/issues/513. The current request has a nice summary of the cottage industry of "blog articles that explain how to reboot & wait": https://github.com/ansible/ansible/issues/16186
- Projects are structured in a quite "sparse" folder structure. A small project usually has 25 files in 20 folders and 18 of them are "main.yml" which is probably a conspiracy to annoy me. The main feature an editor plugin for ansible needs is not syntax highlighting but "use second-to-last folder name instead of filename on tabs".
-