Here is a playbook for understanding the Ansible test with variables types
By default psql write the last 500 commands in the ~/.psql_history file, if like me you want to have a more precise information of who, when and where psql was used, here is a psql_history file setup.
Jinja2 templating with Ansible is powerfull and sometimes you could have some headache for positionning the result just where you want to respect a configuration file syntax. Following, I will show you how to manage the whitespace control with Jinja2
So you have a list with a number of item which are the /data* path where you want to put your hadoop hdfs data and you want to add after each item the end of the path mount point, here is a solution.
Commands for managing certificates, private keys and keystores Useful to create, change password, remove passphrase, etc…
When you do some things that needs complex data structure, it could be great to acces to the key and value of the complex data structure. You can do it with the lookup magic word.
Some times you have to construct the name of a variable to use it. In previous versions of ansible there was a syntax like this one vars[ ansible_hostname + ‘string’ ] Now, since the Ansible 2.5 you have another syntax very useful