Feature #33449
closed
Tracker #33447: Alternate Content Sources Support Tracker (MVP)
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.
Updated by Ian Ballou about 3 years ago
We should also ensure there is a hammer command to refresh ACSs.
Updated by
Updated by Ian Ballou about 3 years ago
- Target version changed from Katello 4.3.0 to Katello Backlog
Updated by
Updated by Ian Ballou over 2 years ago
As part of this, we need to ensure the ACS API returns a 'last refreshed' parameter for the UI.
Updated by Ian Ballou over 2 years ago
- Target version changed from Katello Backlog to Katello 4.5.0
Updated by The Foreman Bot over 2 years ago
- Status changed from New to Ready For Testing
- Assignee set to Ian Ballou
- Pull request https://github.com/Katello/katello/pull/10083 added
Updated by The Foreman Bot over 2 years ago
- Fixed in Releases Katello 4.5.0 added
Updated by Anonymous over 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|68b2cc92c2bbd3457ed76f00ff1f2bc0d818560d.
Updated by Ian Ballou over 2 years ago
- Category deleted (
Repositories) - Assignee deleted (
Ian Ballou) - Target version deleted (
Katello 4.5.0) - 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.
Updated by Ian Ballou over 2 years ago
- Category set to Repositories
- Assignee set to Ian Ballou
- Target version set to Katello 4.5.0
Updated by The Foreman Bot over 2 years ago
- Pull request https://github.com/Katello/katello/pull/10152 added