docs: add renku session RFC

[vigsterkr]

Description

add the renku session sub-command RFC

[olevski]

Looks good to me. Are the last two sections meant to be blank - ie just have questions with no answers?

[rokroskar]

this is great, thanks @vigsterkr for separating it out from the implementation. I still don't fully understand how you intend to find the sessions in commands that require a session ID without knowing which provider to query. I guess it might not matter much in practice, but it seems unnecessary to fetch all lists of sessions from all providers every time. Either we should encode the provider name in the session id, e.g.

renkulab.io/<id>
docker/<id>

or use a --provider flag in those commands as well. I prefer the first option because it's less typing for the user... but we have to come up with a good scheme.

[vigsterkr]

this is great, thanks @vigsterkr for separating it out from the implementation. I still don't fully understand how you intend to find the sessions in commands that require a session ID without knowing which provider to query. I guess it might not matter much in practice, but it seems unnecessary to fetch all lists of sessions from all providers every time. Either we should encode the provider name in the session id, e.g.

renkulab.io/<id> docker/<id>

or use a --provider flag in those commands as well. I prefer the first option because it's less typing for the user... but we have to come up with a good scheme.

the primary reason was to avoid the explicit mentioning of the provider in some cases (see when dealing with session_id) in order to avoid unnecessary typing on the CLI by the user. pluggy by default calls all the registered plugin hooks, but of course there's a way around this behaviour... but i thought that the overhead on the backend side is less than the gained value of not typing things out. This week we talked out prefixing the session_id (mentioned above) with the provider, but to be honest then this adds additional string processing (prone to errors) on the backend side. in this case i'd rather just go with the explicit requiring the -p/--provider <provider> flag from the user. coz essentially it'll do the same thing on the end of the day (from pluggy perspective), but we'd just use the user provided provider instead of doing some string processing for extracting the provider type and the session_id

[rokroskar]

in this case i'd rather just go with the explicit requiring the -p/--provider flag from the user

That's fine - the default can be to cycle through all of them but having a consistent interface where one can specify a provider makes sense to me.

[rokroskar]

two small comments but then I think we're finally done :)