I don't think the Git issue framed it well. Pinning this on a single meeting or interaction makes it easy to trivialize As someone who uses Ansible a lot, I g

I don't think the Git issue framed it well. Pinning this on a single meeting or interaction makes it easy to trivialize As someone who uses Ansible a lot, I giggled. Once. Afterwards I figured out how to disable it because the novelty was gone. The output this creates is a slog. Now I 'have' to remember to create Ansible.cfg files across countless projects because someone thinks this is that funny. That's the most portable approach; it's the best way for contributors. Otherwise I'd set the environment variable on all of my shells and call it done. I forget so often that I've been trained to cancel a playbook as soon as I see a cow from fact gathering. It's more of an annoyance than a real problem. Anyone with cowsay installed on their controller (this isn't always a workstation or human) is initiated in the 'know how to disable this' crew, and gets to regularly attend meetings I feel the feature would work better randomly appearing. Maybe make it visually useful, automatic on the slowest-known run. It retains the novelty because it isn't a constant.