See also: ‣
We currently do not support session secrets in 2.0. We built ‣ for Renku 1.0, and now we want to bring this functionality to 2.0.
In addition, we want to solve a few issues that users have given us feedback about on the Session Secrets functionality in 1.0:
From https://renku.discourse.group/t/start-session-with-secrets-linked-to-it/1089 (‣):
I don’t want to have to go to start with options every time to have my secrets in my session (1.0).
I want to convey to users that a secret is “required” in a session.
From ‣:
I can’t customize where each secret should be mounted in my session.
<aside> ❗
There are technical reasons for not letting multiple secrets not be mounted in different places.
</aside>
I can’t give the secret file name something different than the name of the secret in RenkuLab.
The core of the idea for Session Secrets in 2.0 is that they are tied to a session launcher. In Renku 1.0, the session secrets can only be configured in Start with Options. This means that for projects that use secrets, users have to go to Start with Options every time they launch a session, a click through the UX to add the secrets they need. In 2.0, we will save this configuration in the session launcher.
User Secret: A secret the user enters, and is only available to them.
Session Secret: A secret that is made available in a session. In 2.0, a session secret is configured on the session launcher.
Data Connector Credentials: A subset of User Secrets that are used specifically for credentials for Data Connectors.