tektoncd / tektoncd/pipelines-as-code
How to allow a user/bot to trigger CI across all PAC configured Repositories
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 214
- Forks
- 144
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 27
Description
Currently, if we want to allow a bot like dependant to trigger CI when it creates a pull request we need to
add the bot name in OWNERS file.
if PAC is confiured for multiple repos we need to add bot in all repo's owners file.
so the request is to provide a PAC across way to allow a user/bot not member of org/owner to trigger CI.
One way could be could be
- we can create add the users in configmap and use it to filter in the controller
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
Review the existing OWNERS-based trigger authorization and the controller path that filters pull-request events. Compare that behavior with the proposed PAC-wide ConfigMap allowlist; done means an approved user or bot can trigger CI across configured repositories without being added to each repository's OWNERS file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go, kubernetes
- Domain
- authorization, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100