Make report, puppet classes and environments importing asynchronous using foreman-tasks
There are already 90% done on foreman-tasks side so we can just move it to core. For importing puppet objects it might make sense to keep synchronous way still available.
Refs #15779 - move the foreman-tasks to own bundle group
This makes it easier to achieve a minimal setup, that might be needed for
things like plugins building etc.
The original PR got vetted in the packaging phase and including
foreman-task as dependency of Foreman was refused. We need to rethink
our approach for getting the foreman-tasks functionality available
inside the core and take less obtrusive approach by making the
transition in several steps, until the foreman core will get on
future-parity with foreman-tasks which would effectively mean tasks in
To clean the tasks that were created while using the original changes,
you can run:
TASK_SEARCH="label = Actions::Foreman::Report::Import
OR label = Actions::Foreman::PuppetClass::Import"\
This reverts commits
#19 Updated by Dominic Cleal almost 5 years ago
Debian package tests of
foreman have been failing since 25/11 (e.g. http://ci.theforeman.org/job/systest_foreman/11422/) as the dependency isn't correctly packaged. RPM builds of
foreman have been failing since the same as bundler.d/foreman_tasks.rb is unpackaged.
The packaging PRs were and are still outstanding - if they were finished, worked and tested then it might have been feasible, but they were not.