Restrict access to change project configuration
Open
Nobody has claimed this yet.
enhancement
micall
- Dominant language
- Python
- Stars
- 21
- Forks
- 11
- Avg merge
- 12h 5m
- Merged PRs (30d)
- 24
Description
Everyone should be able to view the details of the pipeline and project configuration, but only MiSeq managers should be able to change the configuration.
Once access is restricted, we can add links to the menu.
- Research how Rails supports roles, and maybe admin routing.
- Restrict access.
- Add links to menu.
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 researching how Rails supports roles and admin routing, as requested in the issue. Then inspect the project configuration and menu entry points to determine where viewing, changing, and linking are handled. Done means everyone can view configuration details, only MiSeq managers can change them, and the relevant menu links are present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rails
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100