- What is the nature and description of the request?
The customer is requesting an Import/Export feature for the Private Automation Hub (PAH). Currently, PAH allows synchronization of Ansible Collection content from external Galaxy servers like galaxy.ansible.com and console.redhat.com, but it lacks a bulk export process. The customer would like the ability to bulk export Ansible Collections, similar to the existing capability in Red Hat Satellite, which also uses Pulp as its backend.
- Why does the customer need this? (List the business requirements here)
The customer, particularly in disconnected environments, needs a more efficient method to manage Ansible Collections in their Private Automation Hub. Without a bulk import/export feature, updating content in disconnected environments is time-consuming, limiting the operational effectiveness of AAP and PAH in these environments. This functionality is critical to enabling the customer to keep their environments up to date without manual workarounds.
- How would you like to achieve this? (List the functional requirements here)
A bulk export/import process for Ansible Collections in the Private Automation Hub, similar to what is available in Red Hat Satellite, allows easy movement of content between connected and disconnected environments.