nebari-dev / nebari-dev/nebari-docs
[DOC] - Document scopes for each service within Nebari and what that gives you access to
Open
Nobody has claimed this yet.
area: documentation 📖
- Dominant language
- No language data
- Stars
- 21
- Forks
- 40
- Avg merge
- 19h 50m
- Merged PRs (30d)
- 6
Description
Preliminary Checks
- This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions
Summary
Document scopes for each service within Nebari and what that gives you access to.
Steps to Resolve this Issue
1.Document Keycloak scopes
2. Document conda-store scopes
3. Document Jupyterlab scopes
4. Document Jupyterhub scopes
5. Document Grafana scopes
What else needs put here?
...
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 by gathering the scope definitions for Keycloak, conda-store, JupyterLab, JupyterHub, and Grafana. Document each service's scopes and the access granted by them; done means all five listed services are covered and any additional services are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100