Skip to main content

Migrating to 2.1.0

Migration Guide​

Here you can find the needed steps to upgrade your current Witboost installation to v2.1.0. Please refer to the release notes for a detailed list of changes and improvements. This guide is intended for users who are currently running Witboost version 2.0.0 or earlier and wish to upgrade to version 2.1.0.

Follow these steps to migrate from the previous version to Witboost version 2.1.0:

Backup Your Data​

Before starting the migration, ensure you have a complete backup of your database and configuration files.

Update Dependencies​

Ensure all the dependencies in the Helm files are updated to their compatible versions for 2.1.0. Refer to the published Helm chart for details.

Upgrade Steps​

CGP​

Changes:

  • The logic behind the way policy violations and metric results are displayed in the marketplace has been updated. Refer to the documentation (User Manual > Managing Policies > Governance Entity Lifecycle section Resource evaluation status) for additional details

Migration:

Important! This version includes a database migration that may take a few minutes to complete. Don't worry if the Coordinator/CGP instance takes some time to start on the first launch after the upgrade, and adjust any related timeouts accordingly.

If you prefer to opt for a manual database migration please reach out the Witboost development team for assistance.

Hasura​

The first run of the updated Coordinator will migrate the CGP database. Execute the following steps on Hasura to keep it aligned:

  • Reload all the metadata (<hasura-host>/console/settings/metadata-actions)
  • Delete all the inconsistent objects (<hasura-host>/console/settings/metadata-status)

Core​

Changes

In this release, the new EntitySearchPicker has been introduced inside witboost. It includes filters that are Practice Shaper aware and features a better user experience. This picker can replace the old (but still supported) EntityPicker and ReadsFromPicker.

Migration

To migrate the EntityPicker and ReadsFromPicker please refer to the EntitySearchPicker page in documentation.

In order to make the above Picker work, it is recommended that the events are enabled and configured in the Coordinator.

This version introduces some changes in authentication providers. The environment used by auth.providers.simple_ldap is the environment you set in auth.environment, so if you set auth.environment: production the application expects a configuration like auth.providers.simple_ldap.production. In the absence of the configuration auth.environment, the default environment that will be used by simple_ldap is development, so the full path is now auth.providers.simple_ldap.development. Please make sure you have a key under auth.providers.simple_ldap that matches the environment set in auth.environment.