argoproj / argoproj/argo-workflows
Separate the credentials between read/write workflow artifacts
Open
area/artifacts
type/security
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
# Use Cases
When would you use this?
More fine-grained access control for different teams. For example, some teams only need read access to workflow artifacts.
---
**Message from the maintainers**:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by clarifying the credential model and affected workflow-artifact access paths, then define how read-only and read/write teams are represented and validated; done means those access levels can be configured separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100