[ENH] - Ability to start stopped shared app, by NOT author

[aktech]

Feature description

Imagine two users, Alice and Bob.

Alice creates an app named "Alice in Wonderland" and shares it with Bob. Now when the app is stopped after a while, say by idle culling and Bob access that app, he can't use the app as it's stopped.

We need the ability to start the app "Alice in Wonderland" by Bob.

The assumption is Bob has sufficient permissions in JupyterHub to start the app (otherwise 403).

Value and/or benefit

Following problems will be solved:

• The problem of keeping the app always alive (causing cost) will be solved.
• The problem of being able to access a stopped app, when the original author is not available.

Anything else?

No response

[kcpevey]

The assumption is Bob has sufficient permissions in JupyterHub to start the app (otherwise 403).

What roles are required for "sufficient permissions"?

[aktech]

What roles are required for "sufficient permissions"?

We need a custom role with scope "servers" (this can be limited by servers of a user or group as well) for the user to have permissions to start the app.

[kildre]

@aktech This is only for Starting an app correct? A shared user still cannot Stop an app?

[aktech]

@aktech This is only for Starting an app correct? A shared user still cannot Stop an app?

Technically yes, but not enabled by backend at the moment, but I would say to frontend should make an API call to stop (just like other stop app call) and if the response is 4xx then message user, you don't have permissions to stop.

So that if we enable stopping shared app in future then it would work right away without any frontend changes.