Project

General

Profile

Actions

Feature #18618

closed

Use Dynflow as an ActiveJob backend

Added by Daniel Lobato Garcia about 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Notifications
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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.


Related issues 3 (1 open2 closed)

Related to foreman-tasks - Feature #8130: Add support of async puppet / chef report processingNew10/28/2014Actions
Related to Foreman - Bug #20908: Postpone the initialization of dynflowClosedIvan Necas09/12/2017Actions
Related to foreman-tasks - Bug #18673: Remove initialization code in favor of DynflowClosedDaniel Lobato Garcia02/24/2017Actions
Actions #1

Updated by The Foreman Bot about 7 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
Actions #2

Updated by Anonymous almost 7 years ago

  • Related to Feature #8130: Add support of async puppet / chef report processing added
Actions #3

Updated by Anonymous over 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #4

Updated by Marek Hulán over 6 years ago

  • translation missing: en.field_release set to 240
Actions #5

Updated by Ivan Necas over 6 years ago

  • Related to Bug #20908: Postpone the initialization of dynflow added
Actions #6

Updated by Ivan Necas over 6 years ago

  • Related to Bug #18673: Remove initialization code in favor of Dynflow added
Actions

Also available in: Atom PDF