Witboost Migration
This feature automatically transforms witboost configuration file (values.yaml
) to make it ready for the target Witboost version you want to install.
The transformation is accomplished by applying a sequence of migrations that are required by each version update.
This CLI supports transformation of configuration files from a minimum Witboost Version 2.3.0 i.e. if your current Witboost deployment is older, you will need to manually migrate to version 2.3.0.
This CLI supports transformation of stable releases only
Migration Workflow
This command requires the CLI to be initialized (refer to the witboost init command). This step is very important because it needs to:
- understand what is your current version
- fetch the rules that must be applied to your configuration file
Initialize the CLI
./witboost-infra init --current-version "2.3.2" --registry-username "foo" --registry-password "xyz"
Once the initialization is complete, your configuration file will look similar to this.
currentVersion: 2.3.0
availableVersions:
- 2.3.0
- 2.3.1-rc.1
- 2.3.1-rc.2
- 2.3.1
- 2.3.2
- 2.3.3
In this example, the user has selected 2.3.0
as the current version, and can upgrade witboost to versions 2.3.1
, 2.3.2
, or 2.3.3
(release candidates are not supported).
Start the migration
With all the prerequisites in place, we can proceed with the migration, using the transform
command. In the following example, we specigy the version 2.3.2
as a target of the migration.
./witboost-infra transform --user-values user_values.yaml --target-version "2.3.2"
[2025-10-03 12:21:11] info: Transform from version 2.3.0 to 2.3.2
[2025-10-03 12:21:11] info: Writing the transformed file to: /Users/jhob.doe/.witboost/output/transformed_user_values.yaml
Configuration migration to version 2.3.2
has been successfully completed.
Command details can be referenced from transform detailed under Command-reference section.