Mr.X

# -*- coding: utf-8 -*-

# Copyright: (c) 2013, Dag Wieers (@dagwieers) <dag@wieers.com>
# GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt)

from __future__ import absolute_import, division, print_function
__metaclass__ = type


DOCUMENTATION = r'''
---
module: set_fact
short_description: Set host variable(s) and fact(s).
version_added: "1.2"
description:
    - This action allows setting variables associated to the current host.
    - These variables will be available to subsequent plays during an ansible-playbook run via the host they were set on.
    - Set C(cacheable) to C(true) to save variables across executions using a fact cache.
      Variables will keep the set_fact precedence for the current run, but will used 'cached fact' precedence for subsequent ones.
    - Per the standard Ansible variable precedence rules, other types of variables have a higher priority, so this value may be overridden.
options:
  key_value:
    description:
      - "The C(set_fact) module takes C(key=value) pairs or C(key: value) (YAML notation) as variables to set in the playbook scope.
        The 'key' is the resulting variable name and the value is, of course, the value of said variable."
      - You can create multiple variables at once, by supplying multiple pairs, but do NOT mix notations.
    required: true
  cacheable:
    description:
      - This boolean converts the variable into an actual 'fact' which will also be added to the fact cache.
        It does not enable fact caching across runs, it just means it will work with it if already enabled.
      - Normally this module creates 'host level variables' and has much higher precedence, this option changes the nature and precedence
        (by 7 steps) of the variable created.
        U(https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable)
      - "This actually creates 2 copies of the variable, a normal 'set_fact' host variable with high precedence and
        a lower 'ansible_fact' one that is available for persistence via the facts cache plugin.
        This creates a possibly confusing interaction with C(meta: clear_facts) as it will remove the 'ansible_fact' but not the host variable."
    type: bool
    default: no
    version_added: "2.4"
extends_documentation_fragment:
    - action_common_attributes
    - action_common_attributes.conn
    - action_common_attributes.flow
    - action_core
attributes:
    action:
        details: While the action plugin does do some of the work it relies on the core engine to actually create the variables, that part cannot be overriden
        support: partial
    bypass_host_loop:
        support: none
    bypass_task_loop:
        support: none
    check_mode:
        support: full
    core:
        details: While parts of this action are implemented in core, other parts are still available as normal plugins and can be partially overridden
        support: partial
    delegation:
        details:
            - while variable assignment can be delegated to a different host the execution context is always the current inventory_hostname
            - connection variables, if set at all, would reflect the host it would target, even if we are not connecting at all in this case
        support: partial
    diff_mode:
        support: none
notes:
    - Because of the nature of tasks, set_fact will produce 'static' values for a variable.
      Unlike normal 'lazy' variables, the value gets evaluated and templated on assignment.
    - Some boolean values (yes, no, true, false) will always be converted to boolean type,
      unless C(DEFAULT_JINJA2_NATIVE) is enabled.  This is done so the C(var=value) booleans,
      otherwise it would only be able to create strings, but it also prevents using those values to create YAML strings.
      Using the setting will restrict k=v to strings, but will allow you to specify string or boolean in YAML.
    - "To create lists/arrays or dictionary/hashes use YAML notation C(var: [val1, val2])."
    - Since 'cacheable' is now a module param, 'cacheable' is no longer a valid fact name.
seealso:
- module: ansible.builtin.include_vars
- ref: ansible_variable_precedence
  description: More information related to variable precedence and which type of variable wins over others.
author:
- Dag Wieers (@dagwieers)
'''

EXAMPLES = r'''
- name: Setting host facts using key=value pairs, this format can only create strings or booleans
  ansible.builtin.set_fact: one_fact="something" other_fact="{{ local_var }}"

- name: Setting host facts using complex arguments
  ansible.builtin.set_fact:
    one_fact: something
    other_fact: "{{ local_var * 2 }}"
    another_fact: "{{ some_registered_var.results | map(attribute='ansible_facts.some_fact') | list }}"

- name: Setting facts so that they will be persisted in the fact cache
  ansible.builtin.set_fact:
    one_fact: something
    other_fact: "{{ local_var * 2 }}"
    cacheable: yes

- name: Creating list and dictionary variables
  ansible.builtin.set_fact:
    one_dict:
        something: here
        other: there
    one_list:
        - a
        - b
        - c
# As of Ansible 1.8, Ansible will convert boolean strings ('true', 'false', 'yes', 'no')
# to proper boolean values when using the key=value syntax, however it is still
# recommended that booleans be set using the complex argument style:
- name: Setting booleans using complex argument style
  ansible.builtin.set_fact:
    one_fact: yes
    other_fact: no

- name: Creating list and dictionary variables using 'shorthand' YAML
  ansible.builtin.set_fact:
    two_dict: {'something': here2, 'other': somewhere}
    two_list: [1,2,3]
'''

Name	Type	Size	Permission
__pycache__	Folder		0755
__init__.py	File	0 B	0644
_include.py	File	3.06 KB	0644
add_host.py	File	3.82 KB	0644
apt.py	File	57.4 KB	0644
apt_key.py	File	17.45 KB	0644
apt_repository.py	File	28.39 KB	0644
assemble.py	File	8.76 KB	0644
assert.py	File	2.75 KB	0644
async_status.py	File	4.29 KB	0644
async_wrapper.py	File	11.43 KB	0644
blockinfile.py	File	13.29 KB	0644
command.py	File	12.64 KB	0644
copy.py	File	34.75 KB	0644
cron.py	File	25.57 KB	0644
debconf.py	File	7.55 KB	0644
debug.py	File	2.89 KB	0644
dnf.py	File	58.16 KB	0644
dpkg_selections.py	File	2.35 KB	0644
expect.py	File	8.33 KB	0644
fail.py	File	1.67 KB	0644
fetch.py	File	4.17 KB	0644
file.py	File	39.93 KB	0644
find.py	File	18.73 KB	0644
gather_facts.py	File	2.5 KB	0644
get_url.py	File	26.22 KB	0644
getent.py	File	5.56 KB	0644
git.py	File	55.22 KB	0644
group.py	File	19.57 KB	0644
group_by.py	File	2.41 KB	0644
hostname.py	File	28.12 KB	0644
import_playbook.py	File	2.06 KB	0644
import_role.py	File	3.27 KB	0644
import_tasks.py	File	2.14 KB	0644
include_role.py	File	4.15 KB	0644
include_tasks.py	File	2.64 KB	0644
include_vars.py	File	6.45 KB	0644
iptables.py	File	32.27 KB	0644
known_hosts.py	File	13.5 KB	0644
lineinfile.py	File	23.39 KB	0644
meta.py	File	5.84 KB	0644
package.py	File	3.33 KB	0644
package_facts.py	File	17.71 KB	0644
pause.py	File	3.44 KB	0644
ping.py	File	2.32 KB	0644
pip.py	File	30 KB	0644
raw.py	File	3.57 KB	0644
reboot.py	File	4.64 KB	0644
replace.py	File	11.19 KB	0644
rpm_key.py	File	8.48 KB	0644
script.py	File	4.03 KB	0644
service.py	File	63.85 KB	0644
service_facts.py	File	16.73 KB	0644
set_fact.py	File	5.62 KB	0644
set_stats.py	File	2.6 KB	0644
setup.py	File	10.79 KB	0644
shell.py	File	6.57 KB	0644
slurp.py	File	3.19 KB	0644
stat.py	File	19.62 KB	0644
subversion.py	File	13.22 KB	0644
systemd.py	File	22.82 KB	0644
systemd_service.py	File	22.82 KB	0644
sysvinit.py	File	13.47 KB	0644
tempfile.py	File	3.42 KB	0644
template.py	File	3.1 KB	0644
unarchive.py	File	42.79 KB	0644
uri.py	File	27.78 KB	0644
user.py	File	114.18 KB	0644
validate_argument_spec.py	File	2.99 KB	0644
wait_for.py	File	25.91 KB	0644
wait_for_connection.py	File	3.38 KB	0644
yum.py	File	72.05 KB	0644
yum_repository.py	File	24.82 KB	0644

Upload:

Command:

Filemanager

Server Info

System Info