Actions
Bug #17878
closedAll plugins are disabled after a minor upgrade
Status:
Released
Priority:
N/A
Assignee:
Category:
Plugins integration
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
First impressions of Rudder
Effort required:
Priority:
94
Name check:
To do
Fix check:
Checked
Regression:
Description
When doing a minor upgrade of the server, all plugins are disabled before the upgrade and not re-enabled afterward.
This is very misleading for the users.
It displays the following error message:
******************************************************************************** Due to incompatibility reasons for this specific version all plugins have been disabled. Make sure to update your repo index and install the latest version of your plugins before re-enabling them. You can use the following commands to upgrade your plugins: rudder package update rudder package upgrade-all ********************************************************************************
But running the given commands will not solve anything when applying a minor update.
It will only work on major ones.
It happens when upgrading from 6.0.6 to 6.0.8-nightly
But the plugins should not be changed in a minor update. I think this is an unclean workaround when we broke plugin compatibility in 6.0.4.We should most likely either:
- State than an upgrade disabled all plugins and let the user re-enabled them manually
- Save the plugin state before update and try to re-enable them. This need to differentiate the minor upgrades from the major ones.
Actions