feedback: Access control | Tarantool
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
<…>diately in the existing sessions
and objects, e.g. functions.|Example for granting many privileges at once|
In this example user ‘admin’ grants many privileges on
many obj<…>
https://www.tarantool.io/en/doc/1.10/book/box/authentication/#users
a
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 linked Users and access-control section at the Tarantool documentation URL. The report body is truncated and ends with “a”, so recover the full feedback before deciding what to change; done should mean the reported documentation issue is clearly identified and addressed.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100