[Audit] Sync Plans, Activation Keys, GPG keys, Product
Katello::SyncPlan - for basic CRUD
products (association) - add/removal of products
SyncPlan is somewhat handled through foreman-tasks today
At the moment, the sync schedules are defined within pulp; therefore, when a sync plan runs, it is pulp initiating it. Once the sync is finished, there is a callback to katello (repositories_controller 'sync_complete') to indicate that it is completed. This can trigger a dynflow action (ScheduledSync) so that we'll have some history of it within katello.