-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
2.4
-
None
-
False
-
-
False
- What is the nature and description of the request?
Private Automation Hub sync fails the whole process on the first error.
If we create a remote on Private Automation Hub using the galaxy URL
https://galaxy.ansible.com/api/
with a requirements.yml containing hundreds of collections. During the sync process of the repository related to this remote, if a temporary error occurs or even a 404 the whole sync process fails. It would be good to keep the sync process running in this case so that PAH could gather other collections.
- Why does the customer need this?
The customer uses the PAH as the first option in their AAP implementation. Therefore, it would be great to have this sync process more fault-tolerant.