Feature Overview

When sync collections in the Private Automation Hub, it cycles through all the versions when sync the repositories, at least that the specific version is set.

Background, and strategic fit

When sync remote collections in automation hub:

Repo Management > Remote > Sync any repository (community /rh-certified)

PAH cycles through all the versions when sync the repositories:

example:

---
collections:
  - name: community.zabbix

This happens at least that the specific version is set:

---
collections:
  - name: community.zabbix
    version: '>= 1.9.0'

It should not cycle through all versions if it should look for latest version available instead.