Skip to main content

Migrating to 0.3.0

Migration Guide​

Here you can find the needed steps to upgrade your current Witboost installation to v0.3.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 0.2.0 or earlier and wish to upgrade to version 0.3.0.

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

Upgrade Steps​

Core​

  • Add the permissions builder.policy.global.edit and builder.policy.template.edit in the role and permissions table to all the platform roles that need to edit governance policies. If a user can't edit/add/delete policies from the UI, it means that he/she has no active role with the permissions above.
  • Add the all the permissions in the form builder.dp.deploy.<envName> found in the rbac.permissions table to the needed roles in the role and permissions table. All users with roles that do not include the deploy permission for an environment will not be able to deploy on that environment.
  • In the marketplace.Environment table the environments now have a new field priority that must be filled: the only mandatory change is to assign the value 0 to the "production" environment; for all other environments the priority number will be just used to sort the environments in the UI. Note that a metadata reload of Hasura could be needed to show the new column: this is usually achievable by clicking on "reload" of the marketplace database.
  • The table rbac.roles_subjects in column entity_ref may contain incorrect values for domains. All the domains must be in the form urn:witboost:dmn:<name>, so errors in this table must be solved to align them to the URN convention above.
  • Observability tab in Data Product or Output Port's details page in the marketplace is hidden by default. To change this behaviour and show it, set the property mesh.marketplace.ui.showObservability to true.