Description

A PAH sync of `rh-certified` against CRC Hub will not reflect CRC sync toggles in real time.

If the CRC sync toggles have changed since the CRC `published` repo has changed (i.e. a new artifact has been approved and added to the `published` repo) then PAH will think there are no changes to sync and will tell the PAH user that sync is "Completed".

Steps to Reproduce

How reproducible: always

1. In PAH sync the `rh-certified` repo with a synclist url i.e. https://console.redhat.com/api/automation-hub/content/540155-synclist/
2. Edit the CRC sync toggles for that organization i.e. 540155
3. Ensure no new content has been added to the `published` repo by checking timestamp https://console.redhat.com/api/automation-hub/v3/plugin/ansible/content/published/collections/
4. In PAH sync again right away - PAH sees that the CRC `published` repo timestamp has not changed and it says sync "Completed" without running through entire sync

Actual Behavior

• PAH always uses optimize=true in the remote syncing against CRC Hub - this skips a sync if the timestamp of the server AnsibleRepository has not been changed since the last sync
• Editing the CRC sync toggle does not edit the AnsibleRepository, it edits the AnsibleDistribution
• The timestamp presented using the AnsibleDistribution base_url is the timestamp of the AnsibleRepository not the AnsibleDistribution, i.e. https://console.redhat.com/api/automation-hub/v3/plugin/ansible/content/5910538-synclist/collections/ shows the timestamp of the `published` repo

Possible Solutions

1. When using the AnsibleDistribution base_url, pulp-ansible present a timestamp that gets updated when sync toggle is edited
2. Allow PAH to configure `optimize` to switch it to false, which will always force an entire sync even if there are no changes
   1. Negatives: requires customer intervention, and will always provide long syncs even when no changes have been made

See planned solution in comment

Workaround in AAP 2.3

• For the PAH remote `rh-certified` click “Edit”, click “Save”, click “Sync” - this updates the timestamp of the remote and therefore forces a sync