-
Notifications
You must be signed in to change notification settings - Fork 0
Description
I suggest we work towards a feature to allow user managed JupyterHub groups via /hub/admin#/groups
determine configuration for user servers. And further, that we do it in a way based on JupyterHub's own concepts of groups to avoid implementing this to be specific to a certain identity provider, such as GitHub.
If we do this, we could for example let users of certain groups get certain shared folders mounted in read/write.
Background
FreshDesk ticket from nasa-cryo
at hub.cryointhecloud.com
[...] understand if there are ways to make storage folders only visible and writable by certain GitHub teams and if this is the use model we want to adopt for some of the more resource intensive events we support.
FreshDesk ticket from victor
at victor.2i2c.cloud
[...] if there is a way to create groups that have access to specific shared folders/areas in the hub?
Action points
- Seek agreement to explore this strategy
- Experiment with JupyterHub groups to learn how to read such state from Spawner hooks we may configure
- Propose a UX that is believed to meet needs and also be technically feasible
- Refine and seek agreement on implementing proposed UX
- Implement proposed UX
- Followup with Sam at Victor via https://2i2c.freshdesk.com/a/tickets/509
- Followup with James having spoken with community representatives at nasa-cryo via https://2i2c.freshdesk.com/a/tickets/509