Bug 824483

Summary: [RFE] Allow for hooks within workflow
Product: Red Hat Satellite Reporter: james labocki <jlabocki>
Component: Content ManagementAssignee: Lukas Zapletal <lzap>
Status: CLOSED WONTFIX QA Contact: Og Maciel <omaciel>
Severity: low Docs Contact:
Priority: low    
Version: 6.0.0CC: lzap, mmccune, omaciel
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-12 22:53:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description james labocki 2012-05-23 14:59:33 UTC
Description of problem:
This is a request for a framework which allows hooks to be executed within all parts of workflows. This framework would allow for third party tools to be easily integrated with CloudForms.

Example Story: When the promote button is selected a hook is called (start_promote) which executes a script (created by customer, consultant, or third party software vendor). This script would insert a record into a third party tool (such as remedy or BMC). System Engine would not start the promotion, instead it would set the status to "waiting for response from $hook_name". Upon completion of workflow in third party tool the third party tool would call System Engine API and change the status from "waiting for response from $hook_name" to "approved". At this point, System Engine would start the promotion.

Comment 1 Lukas Zapletal 2012-05-24 10:33:05 UTC
I am working on a prototype of integrating ruote workflow framework with katello for all its backround processing. I will prepare some demo soon.

http://ruote.rubyforge.org/

It's pretty extensive and such changes could be implemented by changing processes there. They can be defined in Ruby DSL or XML files. Taking.

Comment 3 Lukas Zapletal 2014-03-12 10:27:56 UTC
Bug is irrelevant because Foreman supports foreman_hooks plugin.

Comment 4 Bryan Kearney 2014-03-12 22:53:29 UTC
Closing old bugs which are not relevant based on new UI and CLI