Actions
Feature #18618
closed
Use Dynflow as an ActiveJob backend
Status:
Closed
Priority:
Normal
Assignee:
Category:
Notifications
Target version:
Description
For several backend tasks, we can write jobs using ActiveJob API (very simple), but the executor we had is Dynflow which did not support ActiveJob. This changed with https://github.com/Dynflow/dynflow/pull/216 , so Foreman should take advantage of that and initialize a Dynflow world to be used in its jobs.
A good first place where this could be used is on recurring jobs that need notifications.
Updated by The Foreman Bot almost 8 years ago
- Status changed from New to Ready For Testing
- Assignee set to Daniel Lobato Garcia
- Pull request https://github.com/theforeman/foreman/pull/4316 added
Updated by Anonymous over 7 years ago
- Related to Feature #8130: Add support of async puppet / chef report processing added
Updated by Anonymous over 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 1ed59c634f94dc989491d30baefdf419f3958085.
Updated by Marek Hulán over 7 years ago
- Translation missing: en.field_release set to 240
Updated by Ivan Necas over 7 years ago
- Related to Bug #20908: Postpone the initialization of dynflow added
Updated by Ivan Necas over 7 years ago
- Related to Bug #18673: Remove initialization code in favor of Dynflow added
Actions