Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for scheduling & event based workflows using CloudEvents #557

Open
mszostok opened this issue Nov 15, 2021 · 0 comments
Open

Support for scheduling & event based workflows using CloudEvents #557

mszostok opened this issue Nov 15, 2021 · 0 comments
Labels
area/documentation Related to all activities around documentation area/engine Relates to Engine enhancement New feature or request needs-triage Relates to issues that should be refined

Comments

@mszostok
Copy link
Member

Description

The Argo Events gives us an option to support CloudEvent in Capact.
image

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: Create overlay/tool to consume K8s operators #554). As a result, we don't have problems with timeouts for long-running operations, we don't waste resource for watch actions (polling)
@mszostok mszostok added enhancement New feature or request area/engine Relates to Engine area/documentation Related to all activities around documentation needs-triage Relates to issues that should be refined labels Nov 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Related to all activities around documentation area/engine Relates to Engine enhancement New feature or request needs-triage Relates to issues that should be refined
Projects
None yet
Development

No branches or pull requests

1 participant