The Argo Events gives us an option to support CloudEvent in Capact.
Reason
Have built-in system for creating more reactive execution strategies. Currently, only manual action execution via capact act create/run is supported.
Use cases
System user - Currently, the . Create more reactive execution strategies, e.g. execute action when other action was finished, execute scale/notification action when node is under pressure etc.
Content Developer - Currently engine waits for all steps to be finished before . With events, the workflow can be suspended and resumed when external action was finished (example usage: https://github.com/capactio/capact/issues/554). As a result, we don't have problems with timeouts for long-running operations, we don't waste resource for watch actions (polling)
Description
The Argo Events gives us an option to support CloudEvent in Capact.
Reason
Have built-in system for creating more reactive execution strategies. Currently, only manual action execution via
capact act create/run
is supported.Use cases