-
-
Notifications
You must be signed in to change notification settings - Fork 84
[no refs]: conflicts with 'become' and 'delegate_to' methods #30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[no refs]: conflicts with 'become' and 'delegate_to' methods #30
Conversation
…an't be the same on controller and remote nodes
Hi there. I guess the better solution would be to add |
For example, image to run a playbook on a workstation that need privileges to launch some commands: if you set |
Also, I think it's better run all tasks on remote: in this case, I see no reason to use the |
Even if the playbook is running with escalated privileges, you can set specific task to not to use
For the |
I understand, so I'll try with |
d7bd96f
to
d80e1ac
Compare
It's work! |
366a8b3
to
1996317
Compare
sorry for all these "force-pushed", typing errors as you can see |
No problem at all. Thanks for your help. The new release |
Users may not be the same on controller and remote nodes.
So, if you don't have the same of it, you may run into errors like the follow:
The commit solves this problem and can be considered as a patch level