Chapter 5. Decision environments

Procedure

1. Use de-minimal as the base image with Ansible Builder to build your custom decision environments. This image is built from a base image provided by Red Hat at Ansible Automation Platform minimal decision environment.

   The following is an example of the Ansible Builder definition file that uses de-minimal as a base image to build a custom decision environment with the ansible.eda collection:

   version: 3
   
   images:
     base_image:
       name: 'registry.redhat.io/ansible-automation-platform-25/de-minimal-rhel9:latest'
   
   dependencies:
     galaxy:
       collections:
         - ansible.eda
     python_interpreter:
       package_system: "python39"
   
   options:
     package_manager_path: /usr/bin/microdnf

   Copy to Clipboard Toggle word wrap

2. Optional: If you need other Python packages or RPMs, add the following to a single definition file:

   version: 3
   
   images:
     base_image:
       name: 'registry.redhat.io/ansible-automation-platform-25/de-minimal-rhel9:latest'
   
   dependencies:
     galaxy:
       collections:
         - ansible.eda
     python:
       - six
       - psutil
     system:
       - iputils [platform:rpm]
     python_interpreter:
       package_system: "python39"
   
   options:
     package_manager_path: /usr/bin/microdnf

   Copy to Clipboard Toggle word wrap

Procedure

1. Log in to Ansible Automation Platform.
2. Navigate to Automation Decisions Decision Environments.
3. Click Create decision environment.

4. Insert the following:

   Name

   Insert the name.

   Description

   This field is optional.

   Organization

   Select an organization to associate with the decision environment.

   Image

   This is the full image location, including the container registry, image name, and version tag.

   Pull

   This optional field defines when the Event-Driven Ansible controller attempts to download (pull) the specified container image from the registry before running an automation rulebook. This setting is crucial for ensuring security, consistency, and efficient use of system resources by controlling when the local image cache is updated or reused.

   • Always pull container before running - checks the registry for a new version of the image before every use, even if a local copy exists. This ensures that the freshest content is always used, which is critical for security patches, content updates, and staging environments.
   • Only pull the image if not present before running - checks the local cache of Event-Driven Ansible controller first. If the image is found locally, it is used immediately. A pull from the registry only happens if the image is not found locally. This optimizes performance by avoiding unnecessary downloads and is best for production environments where the content image is stable and faster startup is required.
   • Never pull container before running - never attempts to pull the image from the registry. It only uses an image that has been previously pulled and is present in the local cache. This option guarantees consistency by preventing unintended content changes. It requires the image to be manually pulled to Event-Driven Ansible controller beforehand. If the image isn’t present, the activation fails.

   Credential

   This field is optional. This is the credential needed to use the decision environment image.

5. Select Create decision environment.