-
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
Better examples #409
Comments
/kind documentation |
/assign |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Issues go stale after 90d of inactivity. /lifecycle stale 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. |
/lifecycle frozen |
In this iteration of improving our examples, I'd like to make our examples more like the ones in pipelines i.e. self contained files that a user can
kubectl apply
and then get something useful to happen e.g. something like the cron example we currently have.Couple of conventions:
Each file should contain all of the components needed e.g. the EventListener, TriggerBinding, TriggerTemplates etc.
It'd be tedious to have a new serviceAccount/role for each; so we can reuse one or two service accounts
Would be nice to have a curl command to exercise the Event Listener
(Nice to have) A task that waits for the eventlisteners to boot up and then makes a call to them to verify the behavior...(perhaps we can wrap https://github.com/eddiezane/hook into a task 🤔 )
The text was updated successfully, but these errors were encountered: