From 2908a2c32a81fca78277a22f15fa8e3abe75e092 Mon Sep 17 00:00:00 2001 From: Brian Coca Date: Fri, 27 Oct 2023 03:21:30 -0400 Subject: [PATCH] corrected become same user config docs (#82059) fixes #82057 --- lib/ansible/config/base.yml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/lib/ansible/config/base.yml b/lib/ansible/config/base.yml index 7929bafce9f..29136350e70 100644 --- a/lib/ansible/config/base.yml +++ b/lib/ansible/config/base.yml @@ -119,8 +119,9 @@ BECOME_ALLOW_SAME_USER: name: Allow becoming the same user default: False description: - - This setting controls if become is skipped when the remote user and become user are the same. In other words root sudo to root. - - If executable, it will be run and the resulting stdout will be used as the password. + - When ``False``(default), Ansible will skip using become if the remote user is the same as the become user, as this is normally a redundant operation. + In other words root sudo to root. + - If ``True``, this forces Ansible to use the become plugin anyways as there are cases in which this is needed. env: [{name: ANSIBLE_BECOME_ALLOW_SAME_USER}] ini: - {key: become_allow_same_user, section: privilege_escalation}