Add permissions (e.g. readonly/rw) to Project allow-list elements
- Dominant language
- Go
- Stars
- 24.2k
- Forks
- 7.8k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 239
Description
# Summary
The resource allow-list on the AppProject should be extended with a flag (e.g. `readonly`) to get finer graded permissions on the resource.
# Motivation
The issue arises due to [9973](https://github.com/argoproj/argo-cd/issues/9973). Frankly after the update I had to add Pod and ReplicaSets to the allow list in order to display them properly in the UI. BUT I still want to limit/force the developers to utilize Deployments as interaction point and thus prohibit to create Pods or ReplicaSets
# Proposal
As outlined in the summary and in [9973](https://github.com/argoproj/argo-cd/issues/9973) the allow list could be extended with a flag to either control e.g. readonly behaviour or maybe even more granular permissions, though I cannot think of that right now
Contributor guide
Research direction
Start by reviewing the AppProject resource allow-list and the behavior described in issue 9973. Clarify whether the goal is readonly access or more granular permissions, then define the affected resource interactions and acceptance criteria before estimating implementation work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- authorization, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100