Skip to main content

Migrating to 1.4.0

Migration Guide​

Here you can find the needed steps to upgrade your current Witboost installation to v1.4.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 1.3.0 or earlier and wish to upgrade to version 1.4.0.

Follow these steps to migrate from the previous version to Witboost version 1.4.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 1.4.0. Refer to the published Helm chart for details.

Upgrade Steps​

Core​

  • To enable the access control settings section, make sure that in the values.yaml you have set mesh.platformSettings.enabled to true.
  • If you manually added in your values.yaml the accessRequest action in the actionHandlers section, it is now mandatory to set the boolean value at path actionHandlers.accessRequest.invokeUpdateAcl. If you are using an external service to grant/revoke requests, you can set this to false. However, this value defaults to true if you do not have the accessRequest action specified in your values.yaml: in that case you can leave everything as it is if you want Witboost to behave as it did before this upgrade. As always, check the documentation if you want to learn more about it and its usage.
  • Append AccessControlRequestTemplate to the list of allowed entities under catalog.rules.allow.
  • To keep using access requests, you have to register the access request template of type grant that you can find here
  • To start using revoke requests, register the revoke template by using a default one here.
  • Optionally, set mesh.marketplace.ui.accessControl.enableRevokeRequest as true if you want to be able to revoke access control permissions from the control panel. It defaults to false.
  • If you changed the default theme, now you need to update the custom files according to the new definition. You can check in the documentation how to set up the new theme files.

Follow the docs if you want to further customize access/revoke templates.

Hasura​

  • Make sure that all the tables and columns are correctly tracked after you run the application, and that the metadata are updated.
  • Check that in the table marketplace.ACL there are no rows in status PENDING, or if they are present, ensure that those rows can be safely deleted by the new migration applied.
  • It is strongly suggested to update hasura version to 2.36.1 as the current hasura version installed is obsolete.

CGP​

The default values for the following CGP configurations have been modified:

  • computational-governance-platform.evaluation.task-timeout (default: 20 seconds): This parameter sets the maximum duration allowed for a single policy or metric evaluation, including CUE or remote engine evaluations. Adjust this value based on the size of your data product descriptors and the response times of your remote engines.
  • computational-governance-platform.evaluation.thread-pool-size (default: 32): This parameter governs the allocation of threads for policy and metrics evaluations. Should you anticipate frequent concurrent policy evaluations, it's advisable to adjust this value accordingly. A setting of X implies that approximately X concurrent policy or metric evaluations can be simultaneously executed. If the demand exceeds X evaluations, an execution queue will be formed.