You've might noticed we started using foreman-tasks inside the
foreman-core since  was merged. Unfortunately, we hit issues in the
packaging phase and the proposed workarounds were not accepted (
Based on various discussions, as well as on the fact that
foreman-tasks is already part of infrastructure for pretty wide amount
of plugins (Katello, Remote Execution, Chef, Salt, Ansible, Docker…),
it seems moving foreman-tasks code-base into the core as part of the
Foreman is where people want to get us moving.
Therefore, let me start proposing the plan for moving this subject forward.
The plan would be:
- get the the foreman-tasks-core, that is part of the tasks code
being use both in foreman server and smart-proxy code into separate
- get the foreman-tasks on the same set of rubocop rules the foreman
- fill unit test gaps
- open PR to foreman with the foreman-tasks functionality
- open PR to get the hammer-cli-foreman-tasks inside hammer-cli-foreman
The target version for this would be foreman 1.15.
In the mean time, I would like to kindly ask for trying to
find an acceptable workaround in  and  until this is done.
Also, since this will be pretty large change already, I would like to
avoid radical changes done as part of the PR: as already said,
foreman-tasks has already quite significant user base though various
plugins that we need to support and I would rather prefer keeping
those as additional issues to track and address based on priorities,
as well as going though proper deprecation cycle if we need to
Opinions, comments, questions, concerns (and remember, is also a