Skip to main content

Migrating to 1.2.0

Migration Guide​

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

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

Upgrade Steps​

Core​

  • Append ReverseProvisioningTemplate to the list of allowed entities under catalog.rules.allow
  • If you are using any microfrontend in your witboost installation, this release changes the API contract. Now your microfrontend will receive an object with this structure:
export type MicroFrontendContract = {
  containerId: string;
  theme: DefaultTheme;
  token: string;
  parameters: { [key: string]: any };
};

All additional parameters that you wish your microfrontend to receive and that are defined in the app-config will all end up in the parameters dictionary. Moreover, you will receive the token of the visiting user to perform actions only if he/she is authorized.

Make sure to align your implementation.

Coordinator​

You have the possibility to set an optional config in the coordinator, to extend the compatibility of the coordinator when deploying data products:

provisioning-coordinator {
    supported-kinds = ["dataproduct", "system"]
}

Make sure that the values "dataproduct" and "system" are always included in the array.