Feature Overview

This feature is still highly under discussion

A feature coming with Ansible Automation Platform (AAP) will be something called execution environments [EE].
EE's are designed to allow you to standard an 'automation runtime stack' which can run everywhere consistently, regardless of whether it's on a developers laptop, or in AAP, in cloud, wherever.
EE's essentially are an evolution to virtualenvs in Python/Ansible Tower.
We should be able to call use them from RHACM regardless where they are deployed
A preview in the future of Ansible Automation Platform can be also seen in this blog:
Creating Ansible Execution Environments using Ansible Builder and Shipwright (it's also a tekton integration)
https://docs.google.com/document/d/1bOLlJOI4Foc6y70pFrzgQ2yZ8VHXytqLvj5RCkDhMDE/edit#heading=h.2rwbkvlc14nu
10:58

Now, we are using Execution Environment = Container Image = all required content and executable required to perform Automation

Goals

Execute Ansible flexible on OpenShift Clusters which you ideally can call via Placement
when we create a Cluster in RHACM, how can we use a Playbook to make some changes on the Cluster

when a Policy is violated, how can we use a Playbook to change something on that cluster

CI - CI is running, tests are automated and merged.
Release Enablement <link to Feature Enablement Presentation>
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Polarion: <link or reference to Polarion>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>