This post will cover using special variables that Ansible provides when using blocks for error handling.

I know that it has been a while since i’ve posted. I took a lovely vacation to Japan for 3 weeks and the pre and post trip logistics have me a bit bogged down. This will be a short one.

I just recently discovered that when using a block (and rescue) that two special variables are created that are very useful in limiting the amount of YAML that needs to be written.

This post will cover the process of using bash, podman, and ansible builder.

We’ll tackle this using various files as the container definition. Then a small bash script to run the build, create the container, and upload it to Private Automation Hub. This post is a bit long, check the links if you need to jump around.

Prerequisites

Creating requirements files

Creating a package list file

Creating an execution environment file

Have you ever had a fact that you set earlier in the playbook that can occasionally be empty? If you have, then you know it can sometimes derail tasks later in the playbook.

Luckily jinja offers a default filter that can be used to set a particular value.

Let’s look at an example and how it can be improved by using a default filter. In the example we’re checking to see if there is an IP address before kicking off some node removal tasks in SolarWinds. Note: I’m using my naming scheme here that I use for any include_tasks actions. I’ll cover this in a future post.