No, I can’t. I use it only occasionally, so I don’t remember everything. But many times configurations didn’t work as described in documentation and I had to find a different way to achieve a required result. Sometimes this behavior changed from release to release. This thing doesn’t seem something that I can rely on. But we use it in our company many years, so switch to another tool would be painful.
Comment on Ansible Playbook - How do I reverse engineer a running system?
abecede@lemmy.world 3 weeks agoCould you elaborate a little bit about “full of bugs” and “non-obvious behaviour”? I use Ansible at work for a couple of years already and never encountered anything like that. (I have about 10 playbooks, about 30 roles, about 20 linux servers that I administer)
bizdelnick@lemmy.ml 3 weeks ago
Bo7a@lemmy.ca 3 weeks ago
Same question. But with 100s of playbooks, and thousands of servers. This feels like someone had a bad experience with their first 30 minutes of ansible and gave up before looking at the command reference.
bizdelnick@lemmy.ml 3 weeks ago
No, not 30 minutes. For the first time I spent couple of weeks just for reading documentation and experiments. It was about 8 years ago IIRC. But since that time when I need something more complex than install a package or copy a file, I feel myself like a 30-minutes user because it does not work as I expect.
Bo7a@lemmy.ca 3 weeks ago
Fair enough. I honestly didn’t mean this as an insult. I have seen the same type of review from people who join teams that I’m on when they get told about ansible.
It certainly isn’t perfect. And there was a period of time about 5 years ago where a lot of change was happening at once.
Thanks for sharing your opinion