ansible.utils.loopback_test.rst

ansible.utils.loopback

Test if an IP address is a loopback

Version added: 2.2.0

• Synopsis
• Parameters
• Examples
• Return Values
• Status

Synopsis

• This plugin checks if the provided value is a valid loopback IP address

Parameters

Parameter	Choices/Defaults	Configuration	Comments
ip string / required			A string that represents the value against which the test is going to be performed For example: 127.0.0.1 or 2002::c0a8:6301:1

Examples

- name: Check if 127.10.10.10 is a valid loopback address
  ansible.builtin.set_fact:
    data: "{{ '127.10.10.10' is ansible.utils.loopback }}"

# TASK [Check if 127.10.10.10 is a valid loopback address] *************************
# ok: [localhost] => {
#     "ansible_facts": {
#         "data": true
#     },
#     "changed": false
# }

- name: Check if 10.1.1.1 is not a valid loopback address
  ansible.builtin.set_fact:
    data: "{{ '10.1.1.1' is not ansible.utils.loopback }}"

# TASK [Check if 10.1.1.1 is not a valid loopback address] *************************
# ok: [localhost] => {
#     "ansible_facts": {
#         "data": true
#     },
#     "changed": false
# }

- name: Check if ::1 is a valid loopback address
  ansible.builtin.set_fact:
    data: "{{ '::1' is ansible.utils.loopback }}"

# TASK [Check if ::1 is a valid loopback address] **********************************
# ok: [localhost] => {
#     "ansible_facts": {
#         "data": true
#     },
#     "changed": false
# }

Return Values

Common return values are documented here, the following are the fields unique to this test:

Key	Returned	Description
data -		If jinja test satisfies plugin expression true If jinja test does not satisfy plugin expression false

Status

Authors

• Priyam Sahoo (@priyamsahoo)

Hint

Configuration entries for each entry type 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.