description of the feature

Goals

Provide customers the ability to easily execute automation from Ansible Automation Platform (AAP) on newly provisioned systems that were built with images created by the RHEL image builder service.  This will enable customers to have a workflow to easily create RHEL systems that end up in a fully configured state (including items such as application/workload deployments, security configuration, system configuration, etc.)

Currently, customers can use Image Builder to create images that they can then deploy.  However, customers have a need to perform additional configuration on newly provisioned hosts (such as application/workload deployments, security configuration, system configuration, etc.).  

With the current RHEL image builder workflow, there is not a method that can be used to easily enable systems built from these images to be further automated using AAP after the first boot.  

AAP has a “provisioning callback” functionality that is designed for this use case: running automation on newly provisioned hosts.

This feature is to enable image builder to support creating images that will call a AAP provisioning callback on first boot.  

This could provide an AAP upsell opportunity for people seeing this functionality in image builder and wanting to do further customization in their image builder workflow.

Satellite server currently supports AAP provisioning callbacks when provisioning hosts from Satellite server.  

Requirements

A list of specific needs or objectives that a Feature must deliver to satisfy the Feature.. Some requirements will be flagged as MVP. If an MVP gets shifted, the feature shifts.  If a non MVP requirement slips, it does not shift the feature.

Out of Scope

Documentation Considerations

This functionality would need to be documented.  

Interoperability Considerations

This functionality would rely on the provisioning callback functionality provided in Ansible Automation Platform.  

Questions