Feature #18757
Move foreman-tasks service to Foreman
Pull request:
Fixed in Releases:
Found in Releases:
Description
As per #18618, the dynflow executor is moving over to Foreman, in order to support ActiveJob. Tasks will provide an UI and persistence layer for Dynflow, but Foreman should be able to run jobs without it too.
Part of this effort includes moving the Dynflow executor over to Foreman, which at the moment is managed by the foreman-tasks service.
Related issues
Associated revisions
History
#1
Updated by The Foreman Bot about 4 years ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/puppet-foreman/pull/530 added
#2
Updated by Ewoud Kohl van Wijngaarden over 3 years ago
Updated by - Has duplicate Feature #17467: Configure tasks by default added
#3
Updated by The Foreman Bot over 3 years ago
- Pull request https://github.com/theforeman/puppet-foreman/pull/602 added
#4
Updated by Ewoud Kohl van Wijngaarden about 3 years ago
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman|ee1b7b47365039257077c98426dd20a2fce2ce5a.
Fixes #18757 - Handle dynflow service in foreman core
The dynflow service was moved into core with 1.17. That renamed it to
dynflowd and means the service should be started by default.
For compatibility parameters are provided. This means we must move the
service name detection to the jobs.pp file because that's the only place
we know the actual value.