tektoncd / tektoncd/pipelines-as-code
Change PAC serviceaccount access based on feature enable/disable
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 214
- Forks
- 144
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 27
Description
ref https://github.com/openshift-pipelines/pipelines-as-code/pull/890#discussion_r999784219
auto-configure-new-github-repo is disabled by default so PAC service account shouldn't have access to create repo
we can update pac controller role based on whether user has enabled the feature or not
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 with the discussion in pull request #890 and trace the PAC controller role and the auto-configure-new-github-repo feature setting. Determine how the service account permissions are configured for both disabled and enabled states; done means repository-creation access is absent when disabled and available when enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100