Next steps/action needed:
There are 2 approaches we can take to code refactoring, we have PRs opened to give everyone a better idea what it would look like. We can:
A. move the import logic to core
B. keep it in foreman_templates
We need to decide which way to go, since this essentially blocks further progress (most notable points 2. and 3.). Let us know what you think.
Redmine for foreman_templates tracking all the opened issues.
In case foreman_templates is used, it would be nice to use the foreman_templates plugin from the very beginning and use these templates instead of the seed.d templates.
Regarding “template sync”, there are some regular sync plans currently in foreman / katello:
Katello sync plans for repositories
Remote Execution Tasks
foreman template "sync plans"
What about one “driver” to schedule such regular tasks which can be used within foreman?
The idea of using foreman_templates instead of seeds is interesting. It would save us the step of copying templates from community-templates into foreman/views/unattended.
Having some sort of general scheduler that would run regular tasks would be nice, though it would require some design to meet the needs of all the areas you listed. Maybe another RFE?
This particular item is worth noting in this context. The ability to sync a repository at intervals is something that Katello will need to support natively. Pulp 3 is removing scheduled tasks, so a pre-cursor to eventually moving to it will be to provide sync plan functionality directly. This implies that we will need some core solution for this. So there is one driving factor towards spending the time to build central functionality around this idea.