ns2.col.foo become – Use foo bar

Note

This become plugin is part of the ns2.col collection (version 2.1.0).

It is not included in ansible-core. To check whether it is installed, run ansible-galaxy collection list.

To install it, use: ansible-galaxy collection install ns2.col.

To use it in a playbook, specify: ns2.col.foo.

DEPRECATED

Removed in:

version 5.0.0

Why:

Just some text. This one has more than one line. And one more.

Alternative:

I don’t know of any alternative.

Synopsis

Parameters

Parameter

Comments

bar

string

added in ns2.col 1.2.0

Removed in: version 4.0.0

Why: Just some other text. This one has more than one line though. One more.

Alternative: nothing relevant I know of

Bar. BAR!

Totally unrelated to become_user. Even with become_user=foo.

Might not be compatible when become_user is bar, though.

become_exe

string

added in ns2.col 0.2.0

Foo executable.

Default: "foo"

Configuration:

  • INI entries:

    [privilege_escalation]
become_exe = foo

    [foo_become_plugin]
executable = foo

    Removed in: version 3.0.0

    Why: Just some text.

    Alternative: nothing

  • Environment variable: ANSIBLE_BECOME_EXE

  • Environment variable: ANSIBLE_FOO_EXE

    Removed in: version 3.0.0

    Why: Just some text.

    Alternative: nothing

  • Keyword: become_exe

  • Variable: ansible_become_exe

  • Variable: ansible_foo_exe

    Removed in: version 3.0.0

    Why: Just some text.

    Alternative: nothing

become_user

string

User you ‘become’ to execute the task.

Default: "root"

Configuration:

  • INI entries:

    [privilege_escalation]
become_user = root

    added in ns2.col 0.1.0

    [foo_become_plugin]
user = root

  • Environment variable: ANSIBLE_BECOME_USER

    added in ns2.col 0.1.0

  • Environment variable: ANSIBLE_FOO_USER

  • Keyword: become_user

    added in ns2.col 0.1.0

  • Variable: ansible_become_user

  • Variable: ansible_foo_user

    added in ns2.col 0.1.0

Note

Configuration entries listed above for each entry type (Ansible variable, environment variable, and so on) have a low to high priority order. For example, a variable that is lower in the list will override a variable that is higher up. The entry types are also ordered by precedence from low to high priority order. For example, an ansible.cfg entry (further up in the list) is overwritten by an Ansible variable (further down in the list).

Status

Authors

  • Nobody