I personally am going through a bunch of old roles I have in my playbooks and either throwing them away or rewriting them if they require -b to work. Please feel free to close this issue if it's just The Wrong Way to do it. But perhaps adding something to the README that gently reminds people to not use -b, and write all their roles to sudo when necessary? Also I find the line "The role needs a root access to run. Add sudo: yes in your playbook." in the readme to be deprecated, as I notice that this role has been rewritten to sudo when necessary.
When running ansible with -b (become, or sudo), the error is "Failed to set permissions on the temporary files Ansible needs to create when becoming an unprivileged user. For information on working around this, see https://docs.ansible.com/ansible/become.html#becoming-an-unprivileged-user"
I personally am going through a bunch of old roles I have in my playbooks and either throwing them away or rewriting them if they require -b to work. Please feel free to close this issue if it's just The Wrong Way to do it. But perhaps adding something to the README that gently reminds people to not use -b, and write all their roles to sudo when necessary? Also I find the line "The role needs a root access to run. Add sudo: yes in your playbook." in the readme to be deprecated, as I notice that this role has been rewritten to sudo when necessary.