Ansible - Tag - Gene.Tech https://geneliu.itaghome.win/tags/ansible/ Ansible - Tag - Gene.Tech Hugo -- gohugo.ioengene.liu@live.com (Gene Liu) gene.liu@live.com (Gene Liu)This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.Thu, 28 Jan 2021 00:00:00 +0000 Ansible from_yaml Filter https://geneliu.itaghome.win/2021-01-28-ansible-fromyaml/ Thu, 28 Jan 2021 00:00:00 +0000 gene.liu@live.com (Gene Liu) https://geneliu.itaghome.win/2021-01-28-ansible-fromyaml/ The Ansible from_yaml filter can be used to simplify data manipulation with formatted data.

An example of the list data type:

Without a filter

I have to use both strip and split functions, which is error-prone.

glusterfs_node_hostname_base: |
  {% for item in glusterfs_node|unique %}
  {{ hostvars[item].get('ansible_hostname') }}
  {% endfor %}

## gluster requires unique hostname or nodename while probing peers, here glusterfs_node_hostname 
## stores all glusterfs node's hostname for a validation purpose
glusterfs_node_hostname: "{{ glusterfs_node_hostname_base.strip().split('\n') | default([]) }}"

With from_yaml filter

glusterfs_node_hostname_base: |
  ---
  {% for item in glusterfs_node|unique %}
  - {{ hostvars[item].get('ansible_hostname') }}
  {% endfor %}

## gluster requires unique hostname or nodename while probing peers, here glusterfs_node_hostname 
## stores all glusterfs node's hostname for a validation purpose
glusterfs_node_hostname: "{{ glusterfs_node_hostname_base | from_yaml }}"
]]>