Ansible – Simple module
In this post, we’ll review Ansible module development.
I haven chosen to make a maven module; not very fancy, but it provides a good support for the subject.
This module will execute a maven phase for a project (a pom.xml is designated).
You can always refer to the Ansible Module Development page.
Which language?
The de facto language in Ansible is Python (you benefit from the boilerplate), but any language can be used. The only requirement is being to be able to read/write files and write to stdout.
We will be using bash.
Module input
The maven module needs two parameters, the phase and the pom.xml location (pom).
For non-Python modules, Ansible provides the parameters in a file (first parameter) with the following format:
pom=/home/mohamed/myproject/pom.xml phase=test
You then need to read this file and extract the parameters.
In bash you can do that in two ways:
source $1
This can cause problems because the whole file is evaluated, so any code in there will be executed. In that case we trust that Ansible will not put any harmful stuf in there.
You can also parse the file using sed (or any way you like):
eval $(sed -e “s/([a-z])=([a-zA-Z0-9\/.])/\1=’\2’/g” $1)
This is good enough for this exercise.
We now have two variables (pom and phase) with the expected values.
We can continue and execute the maven phase for the given project (pom.xml).
Module processing
Basically, we can check if the parameters have been provided and then execute the maven command:
#!/bin/bash
eval $(sed -e “s/([a-z])=([a-zA-Z0-9\/.])/\1=’\2’/g” $1)
if [ -z “${pom}” ] || [ -z “${phase}” ]; then
echo ‘failed=True msg=”Module needs pom file (pom) and phase name (phase)”‘
exit 0;
fi
maven-output=$(mktemp /tmp/ansible-maven.XXX)
mvn ${phase} -f ${pom} > $maven-output 2>&1
if [ $? -ne 0 ]; then
echo “failed=True msg=\”Failed to execute maven ${phase} with ${pom}\””
exit 0
fi
echo “changed=True”
exit 0
In order to communicate the result, the module needs to return JSON.
To simplify the JSON outputing step, Ansible allows to use key=value as output.
Module output
You noticed that an output is always returned. If an error happened, failed=True is returned as well as an error message.
If everything went fine, changed=True is returned (or changed=False).
If the maven command fails, a generic error message is returned. We can change that by parsing the content of maven-ansible and return only what we need.
In some situations, your module doesn’t do anything (no action is needed). In that case you’ll need to return changed=False in order to let Ansible know that nothing happened (it is important if you need that for the rest of the tasks in your playbook).
Use it
You can run your module with the following command:
ansible buildservers -m maven -M /home/mohamed/ansible/mymodules/ –args=”pom=/home/mohamed/myproject/pom.xml phase=test” -u mohamed -k
If it goes well, you get something like the following output:
localhost | success >> {
“changed”: true
}
Otherwise:
localhost | FAILED >> {
“failed”: true,
“msg”: “Failed to execute maven test with /home/mohamed/myproject/pom.xml”
}
To install the module put it in ANSIBLE_LIBRARY (by default it is in /usr/share/ansible), and you can start using it inside your playbooks.
It goes without saying that this module has some dependencies: an obvious one is the presence of maven. You can ensure that maven is installed by adding a task in your playbook before using this module.
Conclusion
Module development is as easy as what we briefly saw here, and in any language. That’s another point I wanted to make and that makes Ansible very nice to use.