Upgrading unmanaged configuration
Warning
This feature is currently in beta. It may change in a future version without prior notice. See the Beta Features page for the full list of beta features and their planned release. If you’re using this feature, we encourage you to share your feedback to help with the evaluation process.
Note
If your onsphere instance is running using a managed system check this page Upgrading swarm configuration.
Warning
Before doing anything, you should first make sure the host running the stack has enough free disk space remaining to perform an update. (Each new module takes around 500MB).
Warning
The following process aims at minimizing services interruption time but restart of service will always create a downtime.
Warning
If MongoDB doesn’t start during the upgrade process, check if it has been upgraded to a new major version. If so, the MongoDB fail to start after update guide will help you resolve the issue.
Warning
Before any changes be sure to check the changelog and upgrade guide of your version to see if you need a data migration before upgrading.
Ensure that the Composer version is at least the same as the wanted version
Update the configuration-dispatcher version by editing the compose-file or the helm chart
dispatcherVersionfield.Pull the updated schemas
Update your configuration by applying patches
Run the configuration validation (in vscode you use
ctrl+p->>osp: Validate configuration)If the validation is successful push the updated configuration, otherwise try to see in the changelog if your error is linked to a breaking change you missed
Upgrade all other modules