Feature request: non-privileged users can only launch session with default settings

[LiliGasser]

renkulab.io can be used to deploy apps, e.g., using streamlit, for other users. These other users can launch a session and interact with the app (change input, make calculations, export output).

Request: They should only be able to launch a session with the renku.ini default settings and not be allowed to adjust those, e.g., they are just not displayed for them in the UI.

Who is a non-privileged user: Can either be decided by the owner or somehow linked to their member role. Whatever makes sense to implement.

Please let me know if you have questions or need further clarification of the request.

@rokroskar

[rokroskar]

I think this makes sense - in terms of resource requests, I guess there might be a limit for anonymous sessions specified for the instance that is lower than the user-defined project defaults. In that case the lower of the two will be used. But for things like the URL to open up once the server is booted up, that should be non-controversial.

[ciyer]

Thanks for this suggestion! I have been thinking about this a bit, and I and think the better way to approach this is to introduce support for Apps as a new category of session, distinct from the existing dev sessions. This will allow us to design solutions and provide UX that is optimized for this flow.

If you agree with this approach to your request @LiliGasser I can put a proposal together.

[LiliGasser]

This sounds good to me. The distinction between apps and the existing solution with dev sessions seems valuable to me and would help me with sharing output from the projects.

Thanks @ciyer . I am happy to discuss the proposal if needed from your side.