oxidecomputer / oxidecomputer/v-api
GitHub organization mapper
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 8
- Forks
- 5
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 59
Description
Currently we can map permissions based on a GitHub username, but not on the organizations that a GitHub user belongs to. This will require increasing the permission scope that we ask from GitHub logins. Using the expanding scoping should be optional to the application integrating with v-api.
Contributor guide
No contributing guide indexed for this repository
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 by tracing the existing GitHub username-based permission mapping and the GitHub login permission scope handling. Define how organization membership should affect permissions and how an integrating application can opt into the expanded scope; done means both behaviors are supported without requiring the broader scope by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100