At some point in my organization's press toward Ansible, I came to the realization that Ansible the product is yet another layer of abstraction that is there for its own sake, and of dubious value. I converted a simple script to patch stuff, something that is trivial to write and run, and the yum module behaves different enough from the command-line yum that I have to learn a different way to get and parse the output. AWS logs also behave the same way, impossible to take up and read, quickly, trivially. Why do people read logs? To find out what happened, and do so quickly. Someone will argue that logs are so verbose we need to make them machine-friendly vs. people-friendly, so we can make tools to process them. Somewhere in the past 5 years we've gone toward making things more tool-friendly that humans can no longer interact with them in meaningful way. Some time in the future when something else supplants Ansible, shell will still be there, and still works. Meanwhile, I crib from Ansible docs and StackOverflow just to get things to work the way it did, and the pay-off is ... what exactly?
Edited to add:
Years ago Solaris10 converted the rc boot scripts to what was systemd precursor, SMF. I drank the koolaid, yes! we can build dependencies now, we have service-level kernel events now! I can get rid of daemons and watchdog scripts now! The innards of SMF was indecipherable XML, dependencies grew, you could no longer find a good system view when you ask SMF, and you couldn't easily find and fix what's wrong with the service file. At the time, it was designed to be un-messed-around-with by keyboard-happy warrior greybeard sysadmins, judged to be a source of instability and inconsistency.