Multi Server Permission Model
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
It'd be great if we could select which servers a given user can deploy to from the permission settings.
Describe the solution you'd like
On the user permission page, we add in (Similar to projects selection list), a server selection list. So that the user can only add a new project or service to a given server.
Describe alternatives you've considered
Multiple deployments on multiple server does solve the issue, but the user experience can indeed be improved.
Additional context
No response
Will you send a PR to implement it?
No
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 at the user permission page and compare its existing project selection list with the server selection requested here. Trace how deployment permissions are checked for adding projects or services, then verify that a user can deploy only to selected servers and that existing multiple-server deployments continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authorization, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100