Allow launching user-based images
See original GitHub issueThis is related to #75 & #79 .
We would like to be able to launch a singleuser image that varies based on the authenticated user.
I like the ideas presented in #79 around having a ConfigMap that stores a userId -> option mapping, with a selector presented to the user.
As a stopgap, having singleuser_image_spec
accept a Callable value taking the user
object would be sufficient.
This is something that I will likely have time to work on implementing in the coming months.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Create custom images | Compute Engine Documentation
If you allow users from another project to use your custom images, then they can access these images by specifying the image project...
Read more >Turn images on or off in Gmail - Android
On your Android phone or tablet, open the Gmail app . In the top left, tap Menu Menu . Tap Settings and then...
Read more >Share an AMI with specific AWS accounts
Use the modify-image-attribute command (AWS CLI) to share an AMI as shown in the following examples. To grant explicit launch permissions. The following...
Read more >Get help with the Photos app on your Mac
Click the General button at the top of the Preferences window. Click Use as System Photo Library.
Read more >Personal Release Agreements - Copyright Overview by Rich ...
This section provides and discusses personal release agreements that permit the use of a person's name and image. Personal releases are often referred...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sherl0cks you can look at the ProfilesSpawner in https://github.com/jupyterhub/wrapspawner
if you authenticator can store scope as privilege, you can also adjust the allowed item in the list accordingly.
We ended up using a solution based on wrapspawner - thanks for the link!
I’m closing this issue for now.