Ansible be like:

[DEPRECATION WARNING]: The sudo command line option has been deprecated in favor of the "become" command line arguments. Yadda yadda yadda yadda yadda...

Me:
# grep -rnw . -e 'sudo'
#

Then why the fuck do you keep yelling at my face?

Why are they depreciating Sudo?

@gitpush ansible isn't tied to a particular system and could be run on systems without sudo. They are replacing it with "become", which is able to use a wider range of privilege escalation, like su or other systems, that could be in use

@iKameo you think XD
@Kimmax I see, thanks for explaining :D

In the warning it says "command line option", so maybe it's not in some playbook, but the way you call it? Maybe some --sudo sneaked into the command itself
Happens to me when using the reverse search in the shell

@Kimmax I actually found some sneaky sudos when trying with "-vvv"
How do I get rid of them?

@Drillan767 how are you calling the playbook? It's probably just a parameter on that command line

@Kimmax I'm starting to believe my ansible install is fucked up, I have no problem running my commands via ansible, but if I use ansible-playbook, it WILL try to use sudo -_-

@Drillan767 well there is either a -s when calling ansible-playbook, or it's set in some alias or something. Don't know how the install could be so fucked up that it randomly appends some parameter for you

@Kimmax Can confirm that there's an -s. Can fucking figure out how to remove it 😭

@Drillan767 as I said, check config, especially ~/ansible.cfg, /etc/ansible.cfg and /etc/ansible/ansible.cfg
Also look at what you're executing. Are your sure you don't actually have a -s when running ansible-playbook? Did you overwrite the command with an alias, because you were lazy (.bashrc / whatever shell you use) etc etc
You could strace it and check if it's reading some additional conf somewhere, but crawling through that should be last resort