Read-only api key permission?
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
Current API keys can do a lot of destructive or maybe editing things. Could we limit read-only API keys to read only deployment logs?
Describe the solution you'd like
Implement a key permission system
Describe alternatives you've considered
No.
Additional context
No response
Will you send a PR to implement it?
Yes
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
No files or tests are named. Start by tracing the existing API key handling and deployment-log endpoints, then define which operations a read-only key may access. Done means a permission system exists and read-only keys can read deployment logs without performing destructive or editing actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100