-
Bug
-
Resolution: Unresolved
-
None
-
6.14.0
and also same text at
Section Number and Name:
Synchronizing Ansible Collections
Describe the issue:
Support engineer story: a customer followed that section and decided to synchronize all Ansible collections available to them from Galaxy. The step 8 limiting the collections to sync is just Optional and not followed by the customer.
However, Satellite (or pulp in the version on Satellite) is not capable of such scaled ansible collections numbers (cf. at least bz2251200), and namely there is no need to duplicate all such content blindly to Satellite.
Suggestions for improvement:
Please add there a warning or recommendation to use Requirements.yml field whenever possible, to limit collections being synced. With the arguments of scalability and usefulness reasons.
Additional information:
Setting TestCoverage -> NoCoverage since I don't expect such a warning message would regress.