1. What is the nature and description of the request?
   In AAP 2.5 containerized installation, when re-running the installer to get the newer patch releases, the automation hub API token is reseted.

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

When customer update the AAP 2.5 to get the newer patch releases, their CI/CD Pipelines stop working due to the token reset.

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

In RPM installations, the following parameters exists to avoid the token reset:

generate_automationhub_token 
automationhub_api_token

The AAP 2.5 containerized installer should also use the above parameters to avoid the token being reset.

Reference:
> Automation Hub Variables only for rpm installations
https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html-single/containerized_installation/index#ref-hub-variables

1. List any affected known dependencies: Doc, UI etc..
2. Github Link if any