Obtain an Ansible Job output from Ansible Tower API

 April 27, 2022

A couple of years back, I wrote a blogpost on obtaining the previous Job ID in Ansible Tower workflow. Now, let’s go further and create another module to obtain the output of such a job. Before moving further, I want to specify that I talk about Ansible Tower since this is the most known name for this software, but I could also be talking about AWX or Ansible Controller since those are the same codebase.

Obtain previous Job ID in Ansible Tower Workflow

 November 15, 2020

Ansible Tower allows you to create Workflows, which enable you to create complex workflows by putting together multiple Ansible Playbooks. Ansible Tower Workflows can have some simple logics, such as run different Ansible Playbooks based on the outcome (success or failure) of a previous Ansible Playbook run. Sometimes, though, you need to have more information about a previous Ansible Playbook run than just the outcome. I recently found myself in a situation where I had an Ansible Tower Workflow with two Ansible Playbooks into it, where the first one was performing specific tasks.

Python 2.7 released

 July 5, 2010

Two days ago, with an email to the Python Announce mailing list, Benjamin Peterson announced the release of Python 2.7. This moment is of historical importance for the Python project since 2.7 will be the latest major 2.x release. From now on, only the Python 3.x branch will have additional development. To ease this change, Python 2.7 will get full support for five years. The changes between 2.7 and 3 are easy to apply for the majority of codebases, but I suspect that many projects will not make the deadline.