You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to inject/dispatch triggers in the middle of workflows so that rules can trigger additional workflows when those trigger points are reached. Then, custom triggers registered in a pack can serve as well known synchronization points.
ISSUE TYPE
Feature Idea
EXPECTED RESULTS
trigger my_42_trigger registered in example pack with the following action in a workflow to dispatch it.
I have a data-processing workflow that gets triggered by a sensor when a new server comes online. The workflow gathers data about the server, processes it (using custom actions), and then dispatches/injects the additional triggers once each piece of data is available. This way, the sub-workflows can start as soon as the data they require is available, and the data-processing workflow can be much simpler without having to keep a centralized list of everything that should start once the data is ready.
IMPLEMENTATION THOUGHTS
This could be, as @nmaludy suggested in slack, an action that uses webhooks to kick off the various triggers/workflows.
If the action were in core, however, it could skip the webhook processing, and just inject the trigger. This might work something like the sensor service's dispatch method.
I looked at putting this in the st2 pack, but the st2 client lib doesn't have the ability to kick off triggers, so it makes more sense to make this part of the core pack. Possible names include core.inject_trigger or core.dispatch_trigger. "dispatch" is nice because it mirrors the terminology used in sensors.
Looking at what might be useful in implementing this:
SUMMARY
I would like to inject/dispatch triggers in the middle of workflows so that rules can trigger additional workflows when those trigger points are reached. Then, custom triggers registered in a pack can serve as well known synchronization points.
ISSUE TYPE
EXPECTED RESULTS
trigger
my_42_trigger
registered inexample
pack with the following action in a workflow to dispatch it.EXAMPLE USE CASE
I have a data-processing workflow that gets triggered by a sensor when a new server comes online. The workflow gathers data about the server, processes it (using custom actions), and then dispatches/injects the additional triggers once each piece of data is available. This way, the sub-workflows can start as soon as the data they require is available, and the data-processing workflow can be much simpler without having to keep a centralized list of everything that should start once the data is ready.
IMPLEMENTATION THOUGHTS
This could be, as @nmaludy suggested in slack, an action that uses webhooks to kick off the various triggers/workflows.
If the action were in core, however, it could skip the webhook processing, and just inject the trigger. This might work something like the sensor service's dispatch method.
I looked at putting this in the
st2
pack, but the st2 client lib doesn't have the ability to kick off triggers, so it makes more sense to make this part of thecore
pack. Possible names includecore.inject_trigger
orcore.dispatch_trigger
. "dispatch" is nice because it mirrors the terminology used in sensors.Looking at what might be useful in implementing this:
The text was updated successfully, but these errors were encountered: