Feature #33449
Tracker #33447: Alternate Content Sources Support Tracker
As a user, I can expect my ACSs to be refreshed appropriately
Description
When to refresh:
1) At ACS creation time
2) On a cron-based schedule
-> cron config: https://github.com/theforeman/foreman-packaging/blob/rpm/develop/packages/katello/katello/katello.cron
-> The user can edit the cron config if they choose
3) When an ACS refresh API endpoint is hit
It would also be good to have a rake task to refresh the ACSs.
At refresh time, also update the remote and/or ACS if necessary.
Associated revisions
History
#1
Updated by Ian Ballou 9 months ago
We should also ensure there is a hammer command to refresh ACSs.
#2
Updated by Jonathon Turel 9 months ago
- Target version set to Katello 4.3.0
#3
Updated by Ian Ballou 9 months ago
- Target version changed from Katello 4.3.0 to Katello Backlog
#5
Updated by Ian Ballou about 1 month ago
As part of this, we need to ensure the ACS API returns a 'last refreshed' parameter for the UI.
#6
Updated by Ian Ballou 30 days ago
- Target version changed from Katello Backlog to Katello 4.5.0
#7
Updated by The Foreman Bot 27 days ago
- Assignee set to Ian Ballou
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/10083 added
#8
Updated by The Foreman Bot 18 days ago
- Fixed in Releases Katello 4.5.0 added
#9
Updated by Anonymous 18 days ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|68b2cc92c2bbd3457ed76f00ff1f2bc0d818560d.
#10
Updated by Ian Ballou 17 days ago
- Target version deleted (
Katello 4.5.0) - Assignee deleted (
Ian Ballou) - Category deleted (
Repositories) - Fixed in Releases deleted (
Katello 4.5.0)
Just to be clear, this issue did not take care of the cron job. There is a separate packaging issue for that.
Fixes #33449 - Alternate Content Source refreshing support (#10083)