Chef Server 12: Provide Read-Only RBAC Group
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
Along with completed complete documentation from #19 , customers' most commonly sought use case for RBAC is a read-only group that while not capable of changing the system can view as many aspects of the system as are allowed to members of the Users group.
We should ship this as a built-in group into which Admin group members can assign other users.
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 issue description and the completed documentation referenced in #19, then locate the Chef Server RBAC implementation and its existing Admin and Users groups. Define the built-in group's read-only permissions and verify that Admin members can assign users to it; the payload names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100