Migrate from deprecated features
Datalore On-Premises deprecates the following features from the user interface starting from version 2025.1:
Deprecated feature | New feature | Migration |
|---|---|---|
Secrets | Environment variables as workspace resources | |
SSH keys managed via user settings | SSH keys managed as workspace resources | SSH keys created in the user settings are migrated to the Private workspace resources. For all other workspaces where databases or Git repositories use SSH keys, it is required to add new keys and update SSH tunneling settings for each database outside your Private workspace. |
Git repositories managed as notebook environment packages | Git repositories managed as workspace resources | Git repositories added via notebook environment are migrated to the resources of respective workspaces. Manual SSH key attachment is required. |
In 2024.5, the user interface still provides access to the old entities associated with these deprecated features, but it will soon not be available. To ensure smooth functioning of your projects that are still relying on them, you are required to perform a series of migration procedures.
Procedures
Switch to workspace-level management
Click the avatar in the upper right corner of the screen and select Admin panel.
On the Admin panel, select the Configuration tab.
On the Configuration tab, switch the Enable new workspace-level SSH keys and Git libraries toggle.
In the confirmation dialog, review the resulting changes and click the OK button to launch the migration process.
Migrate secrets
Environment variables are the new alternative to Secrets (soon deprecated). To preserve your secrets, migrate them to environment variables.
Click the avatar in the upper right corner of the screen.
Select Account settings from the menu.
Switch to the Secrets tab.
Click the ellipsis for the secret you want to migrate.
Select Migrate secret to environment variable.
You can find the migrated secret in Environment variables on the left-hand menu of the Home page.
Update Git repositories and databases with SSH keys
Perform this procedure for databases and Git repositories outside your Private workspace that were using old SSH keys.
Add new SSH keys.
On the Home page, select the workspace.
In the selected workspace, go to .
Add a new SSH key as described here.
Update SSH tunneling settings for each database connection that uses this method.
In the selected workspace, go to .
In the database list, right-click the database connection where you want to update SSH tunneling settings.
In the Edit database connection dialog, switch to the SSH tab.
Expand the list under Key pair, and select one of the newly added SSH keys.
Update SSH keys for each Git repository.
In the selected workspace, go to .
Click the repository that was using SSH keys added to your user settings.
In the Edit repository connection dialog, expand the list under SSH key and select one of the newly added keys.
