-
Notifications
You must be signed in to change notification settings - Fork 743
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
Trigger different workflows from single Sensor #174
Comments
This is addressed in upcoming release v0.8, have a look at #162 You will be able to group event dependencies and apply any arbitrary boolean logic for these groups. On top of it, you'll be able to define when to execute triggers on ( any or all ) conditions. |
That looks great! I look forward to trying it out. A quick look at the example seems to indicate that the new functionality I'm looking for is:
So for the Calendar Gateway, I can configure multiple schedules in the ConfigMap, setup a single Sensor with multiple |
Exactly. And the circuit to resolve the groups would be |
Thanks. I didn't notice the This seems like it probably addresses my issue. I'll wait for 0.8 to be released and try it out. |
Hi Team, I have multiple eventsources, when any one of them triggers, I should be able to run the workflows. I have made values dynamic, so single sensor is enough for me. It feels like it should be possible to have a Sensor with multiple triggers defined and when any one of the dependencies triggers sensor should run. I am not able access this link: https://github.com/argoproj/argo-events/blob/master/examples/sensors/webhook-http-dependency-groups.yaml Can you suggest a solution on this? |
Is your feature request related to a problem? Please describe.
I have a use-case where we have many scheduled workflows using the Calendar Gateway.
Right now, for every scheduled workflow, there is a Sensor that is deployed. This feels a little unnecessary as the containers are mostly idle while waiting for a single event to be triggered.
Describe the solution you'd like
It feels like it should be possible to have a Sensor have multiple triggers, so that the Sensor can trigger different workflows.
Describe alternatives you've considered
Kubernetes native Cronjobs offer an alternative, but you can't embed Argo Workflows directly.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: