Chef Server 12: Document RBAC and Tools
Open
Nobody has claimed this yet.
Triage: Try Reproducing
Type: Enhancement
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
Not for the initial release, but it is critical to have full documentation for the RBAC system and reasonable tools to manipulate it.
OPC/EC have presented a tough nut to crack in this regard, so clarification on standard procedure would really help.
The following abilities would be stellar
- Recreate all standard groups and perms as during an org creation.
- Add orphaned users back to the Users group, orphaned admins back to the Admins group.
- If at all possible, a process by which things can be set back to a known good working state. Failing that, fall back on documentation of the oc_bifrost schemas and RBAC system’s functioning to decipher the issue.
The number one unrepresented use-case for RBAC is #32
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 RBAC system and oc_bifrost schemas, then examine the organization-creation behavior and the use case referenced by #32. Define what standard procedures and recovery tools are required for the listed group and permission cases, and document the resulting behavior and known-good recovery path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- authorization, documentation, tooling
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100