Add e2e tests for webhook
Open
Nobody has claimed this yet.
lifecycle/frozen
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
As part of Operator we have added custom webhook implementation to handle
- Adding of proxy related env for all the pods created by tekton during runtime.
- Adding annotation to Triggers Eventlistener in order to handle autocreation of certs for Openshift
right now there are no E2E to test webhook implementation.
This issue is to track the same
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the custom webhook implementation and the existing end-to-end test setup; the issue does not name specific files or test entry points. Add coverage for proxy-related environment variables on runtime-created Tekton pods and annotations on Triggers EventListeners for OpenShift certificate autocreation. Done means both webhook behaviors are exercised by E2E tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100