-
Notifications
You must be signed in to change notification settings - Fork 420
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
Dynamic triggering of triggerGroups #1474
Comments
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-lifecycle rotten It can be part of future roadmap. |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-lifecycle rotten |
/reopen |
@khrm: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This feature sounds really cool, I tried to implement it, not sure if it meets the requirements. In /pkg/template/event.go file, add func ResolveTriggerSelector and applyEventValuesToTriggerSelector
In /pkg/sink/sink.go file, replace func processTriggerGroups
Can such modifications complete this feature? |
Is this code possible? |
I am in the same situation as OP and would find this feature really helpful. |
Feature request
I would like to have the possibility to use interceptor variabels when matching triggers with matchLabels. This would mean that you could define a single eventlistener for multiple repositories and activate specific triggers where labels match something in the payload. Since eventlistener has a long running pod it make sense to me to not have one eventlistener per repository. I know that it is possible to let the eventlistener trigger multipele triggers and let the triggers (via interceptor) filter out if they should continue or not. With many repositories wired to one eventlistener this would create a spike for every event. Being able to use variables on matchLabels would save resources in the cluster by having fewer eventlisteners and only activate the triggers that should actually run.
Use case
For our company this would be a great feature. We have a microservice architecture with many repositories. Every opening to the outside world comes with a lot of extra work (approval, firewalls etc.) so to have a singe eventlistener for multiple repositories is a must.
Example:
The text was updated successfully, but these errors were encountered: