Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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.

Bug is irrelevant because Foreman supports foreman_hooks plugin.

Closing old bugs which are not relevant based on new UI and CLI