Skip to content

Remove yes/no as values for Ansible 'become' #600

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

Merged
merged 5 commits into from
Aug 19, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions en-US/Design.xml
Original file line number Diff line number Diff line change
Expand Up @@ -637,12 +637,13 @@ STEP 14: COMMIT <emphasis>...output omitted...</emphasis> localhost/nexus:latest
</listitem>
<listitem>
<para>
As much as possible, leave the system-wide default as <varname>become: false</varname> or <varname>become: no</varname> and if a single task needs privileges, set <varname>become: true</varname> or <varname>become: yes</varname> on that task.
As much as possible, configure the default setting for <varname>become</varname> to <code>false</code>.
If a single task needs privileges, then set <varname>become: true</varname> on that task.
</para>
</listitem>
<listitem>
<para>
If most tasks in a play require escalated privileges, set the entire play to <varname>become: true</varname> or <varname>become: yes</varname> and possibly selectively set individual tasks to <varname>become: false</varname> or <varname>become: no</varname>.
If most tasks in a play require escalated privileges, then set the entire play to <varname>become: true</varname> and selectively set individual tasks that do not need escalated privileges to <varname>become: false</varname>.
</para>
</listitem>
</itemizedlist>
Expand Down