Install
Works with Drupal: ^10 | ^11Using Composer to manage Drupal site dependencies
Alternative installation files
Download tar.gz
5.67 MB
MD5: 8d2a5f4d50507cbf85b1ea33b160c68a
SHA-1: 2cfcfbb0e51b5a74dbfee06cfeff7f9958a83380
SHA-256: 2d2c0be65d4bbefea78e12afaa99a0b7971b9f0b8caf5026f27eb8788f5f31d0
Download zip
6.03 MB
MD5: e1f95a0fd356e81b128be59dd9abc710
SHA-1: 75380ac1679ebf6b4d1d04756dccf0d6b3c39a79
SHA-256: 69fae8749365b24a28b43268c34cd3d64b0ab2c82ee120017dbcaac3ba54a849
Release notes
SODa SCS Manager 4.7.0 adds an Orphan resources page, expands team member role controls, opens confirmation dialogs in overlays, and fixes demo template builds, triplestore token sync, and expired-session polling.
Upgrade notes
- Update the SCS custom theme for the outlined member rows, the edit button's expanded state, and the WissKI update action layout.
- Build a new demo template version from an installed source WissKI that has the
api-importaccount and the rolewisski_api_import, then activate it, and reset existing demo projects.
Added
- Administration has an "Orphan resources" page that lists Portainer stacks, MariaDB databases and triplestore repositories that still exist in the backend but have no matching SCS Manager stack or component entity, and stacks or components that still point at a deleted project. Each category explains when something counts as an orphan (hover title and description). Selected items can be deleted after a confirmation; deletion runs as a Drupal batch with a progress page (one item per request). Shared infrastructure databases are ignored.
Changed
- Application role controls now expand beneath each member's email in the team editor, with changes applied using Save. Update the SCS custom theme for the outlined member rows and the edit button's expanded state.
- The Varnish cache, snapshot and WissKI update confirmations open in overlays on the application details page.
- The WissKI update confirmation uses primary Update and secondary Cancel buttons side by side. Update the SCS custom theme for the action layout.
- The demo reset confirmation now opens in an overlay on the project page.
- The SCS Administration overview uses Drupal's standard admin menu block page, so Gin and Claro can render it. The custom card grid is gone.
Fixed
- Demo templates: building a version refuses a source WissKI that has not finished its installation, before anything is stopped. Before, the build stopped the WissKI during its installation; it did not start again, and the version was still marked ready. A demo WissKI keeps its own install state when the template is restored into it. Provisioning fails when the WissKI of the template lacks one of the roles of the
api-importaccount, instead of creating the account without them, and an existingapi-importaccount gets the roles too. The Team Folder copy skips.ipynb_checkpoints, and the Jupyter home in a template no longer contains the runtime files, history, workspaces and caches of the source user. Varnish is restarted after the WissKI container starts again (demo build and restore, snapshot create and restore). When the manager issues a new triplestore token for a user (their OpenGDB account was created again), the adapters of the user's running WissKI instances get the new token; a demo restore also writes the current token. Before, such a WissKI kept the old token, so every read and write of its triplestore was refused and the notebook import stored nothing. Build a new demo template version from an installed source WissKI that has theapi-importaccount and the rolewisski_api_import, then activate it, and reset existing demo projects. Related: #3639291. - Demo jobs: a job that finishes within a second (for example a template build that is refused at once) no longer shows "Could not start the demo jobs". The start counts as done when the queue run is still going or has already taken the jobs. Related: #3639298.
- A dashboard, project, application, conversation or demo project page left open after the session expired no longer polls the health status, the notification count, the messages or the demo status forever. The first refused request stops the polling and the status tooltip asks to reload the page. Background requests of an expired session get a plain 403 instead of a redirect to Keycloak, so the log is no longer flooded with "access denied" and "Send authorize request" entries. Related: #3639179.
- The application forms reject a name that an existing application already uses, also when the existing one stores it with a prefix (a WissKI's database, triplestore and stack, or a standalone SQL database or triplestore). Before, a taken WissKI name passed the form and failed only while the WissKI was created ("A database with this application name already exists"). A rejected name is logged with the names it collides with. Related: #3639084.
- The "Add application" dialog shows the reason the server gave when an application cannot be created, for example that the name is taken. Before, it only showed the general list of possible reasons. The Create-Project wizard now also shows a single error message, not only lists of several. Related: #3639084.
- The Create-Project wizard checks each application on the server when you leave its step, before the project is created. A taken name or another invalid value is shown in that step, and you can correct it there. Before, the wizard created the project first, and an invalid application stopped it and every application after it. Related: #3639087.