• What is the nature and description of the request?

The request is to add a field to the Ansible Automation Platform (AAP) Custom Resource (CR) that allows a user to provide the license information directly during deployment. This would eliminate the need to apply the license via a separate playbook after the AAP instance is running.

• Why does the customer need this? (List the business requirements here)

Streamlined Deployment: To simplify the deployment process of AAP on OpenShift by embedding all necessary configuration, including the manifest, into a CR.

GitOps Workflow: To support a declarative, GitOps-style approach where the entire state of the application is defined in a single source of truth (the CR), rather than requiring post-deployment steps.

Reduced Manual Effort: To automate a previously manual or scripted step, reducing the potential for human error and simplifying the overall management of AAP instances.

• How would you like to achieve this? (List the functional requirements here)

Add a new field, such as spec.license, to the AAP Operator's Custom Resource Definition (CRD).

The field should accept the license content, either as a string or a reference to a secret.

The AAP Operator should be able to read this field and automatically apply the license to the running AAP instance during the initial deployment phase.

The operator should handle any updates to the license provided in the CR, if applicable.

• List any affected known dependencies: Doc, UI etc..

Documentation: The documentation for deploying AAP on OpenShift would need to be updated to include the new CR field and its usage.

UI: The AAP Operator's UI, if it exists, should be updated to expose this new field.

Operator Logic: The AAP Operator's internal logic needs to be modified to process the license information from the CR and apply it correctly.

• Github Link if any