Skip to main content

Migrating to 2.4.0

Migration Guide​

Here you can find the needed steps to upgrade your current Witboost installation to v2.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 2.3.0 or earlier and wish to upgrade to version 2.4.0.

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

Upgrade Steps​

Core​

Migration

  • If you're explicitly overriding config catalog.rules.allow (under appConfig in the ui block of the values.yaml file of the Witboost Chart): append SystemPrototypeType, SystemPrototypeTemplate to the catalog.rules.allow list

  • If you're explicitly overriding config backend.csp(under appConfig in the ui block of the values.yaml file of the Witboost Chart):

    In order to correctly visualize Technology icons inside the Extension Manager, the source expression 'blob:' should be added to the img-src directive of the backend.csp config. For example if in the current config is:

    csp:
      connect-src: ["'self'", "http:", "https:", "wss:"]
      img-src: ["*", "'self'", "data:", "https:"]
      script-src: ["'self'", "'unsafe-eval'"]
      script-src-elem: ["'self'", "'unsafe-eval'"]

    It should be changed to:

    csp:
      connect-src: ["'self'", "http:", "https:", "wss:"]
      img-src: ["*", "'self'", "data:", "https:", "blob:"]
      script-src: ["'self'", "'unsafe-eval'"]
      script-src-elem: ["'self'", "'unsafe-eval'"]

    If the directive img-src is not already defined in the csp configuration, 'blob:' should be added along with the other source expressions.

  • A new Backlog section in the Builder allows the creation of System Prototypes. In order to view it, assign the permission builder.system-prototype.edit to one of the roles.

  • The new Extension Manager section in the Administration panel allows users to register and edit Tech Adapters directly from the UI. It is accessible to roles that have the platform.extension-manager.edit permission.

Computational Governance Platform (CGP)​

CUE engine has been upgraded to v0.13.2. Now unused imports are considered errors, remove them, if any, from your policies to avoid blocking the deployment of end users of the platform.

To check whether your policy contains any unused import, just test it from the Governance > Registry page, either against marketplace resources or with a test descriptor like this one:

key: value

The error will appear right after the test starts