How to split an ansible local_action in multiple lines

ansibleansible-playbook

I have a local_action the I would like to split in multiple lines.

  - name: Find geographical region of this server
    local_action: uri url=http://locator/studio/{{ ansible_default_ipv4.address}} method=GET return_content=yes register=locator_output

Best Answer

The task is defined using shorthand syntax. The same result could be achieved by using the regular syntax and delegate_to parameter, like this:

- name: Find geographical region of this server
  uri:
    url: http://locator/studio/{{ ansible_default_ipv4.address}}
    method: GET
    return_content: yes
  register: locator_output
  delegate_to: localhost

Related Solutions

Docker – Running an Ansible command in multiple docker containers

Given the following example output from docker ps:

$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS               NAMES
7e21761c9c44        busybox             "top"                    22 minutes ago      Up 22 minutes                           agitated_yonath
7091d9c7cc56        nginx               "nginx -g 'daemon off"   23 minutes ago      Up 23 minutes       80/tcp, 443/tcp     fervent_blackwell

This playbook will give you an idea of how to capture the data you need and how to run actions iterating on the provided list. It's a very simple example, and you'll have to adapt it to your needs. That's on purpose:

---
- hosts: localhost
  gather_facts: no
  tasks:

  - name: gather list of containers
    shell: docker ps | awk '/{{ item }}/{print $1}'
    register: list_of_containers
    with_items:
      - busybox

  #- name: debug
  #  debug: msg="{{ list_of_containers }}"

  - name: run action in container(s)
    docker_container:
      name: temp-container
      image: busybox
      command: uptime
      cleanup: yes
      detach: yes
    register: result_of_action
    with_items:
      - list_of_containers.results.stdout_lines

The interesting parts are:

Gather the list of containers in a given host (localhost in my example). I've used a plain shell invocation to be able to use awk to filter out the output. The result is stored in a register. Since the input is a list, this will have a direct consequence on how to retrieve the data back, more below. Uncomment the debug task in between to compare the data stored in the register with and without a list.
Iterate over the register's results (container ID) and use the docker_container module to run an action (command parameter). You can use links and volumes_from in your docker_container invocation. Check the on-line documentation of the module for the details.

Ansible jinja2 template: How to loop through sub-elements of interface facts

This is what's required:

{% for iface in ansible_interfaces %}
 {{ iface}} :
 {% if  hostvars[inventory_hostname]['ansible_%s'|format(iface)]['ipv4'] is defined %}
   {{ hostvars[inventory_hostname]['ansible_%s'|format(iface)]['ipv4']['address'] }}
 {% else %}
   No ip address set
 {% endif %}
   MTU: {{ hostvars[inventory_hostname]['ansible_%s'|format(iface)]['mtu'] }}
{% endfor %}

This works. NOTE that you can't have the condition check for a sub-element of (in this case) 'ipv4' like so:

{% if ... ['ipv4']['address'] %}

Because this still assumes that the dictionary has an element 'ipv4', when it doesn't.

I hope this helps someone else.

Best Answer

Related Solutions

Docker – Running an Ansible command in multiple docker containers

Ansible jinja2 template: How to loop through sub-elements of interface facts

Related Topic