Actions
Bug #24288
closed
rudder package should target last version accordingly to the webapp version for plugins
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I hate Rudder for that
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
98
Name check:
To do
Fix check:
To do
Regression:
No
Description
Let's say that we have a webapp in version 8.0.3 when we use the command rudder package list --all, it will give us the list of plugins available and their latest version, so for example, if the latest version of Rudder is 8.0.5, rudder package will target this version as latest version available.
If we try to update the plugin, it will update it to the version 8.0.5, instead of taking the latest version available for version 8.0.3 accordingly to the webapp.
This can lead to incompatible plugin with the current webapp.
Plus, the option --exact-version doesn't seems to work either.
Updated by Elaad FURREEDAN 10 months ago
- Related to Bug #22690: when upgrading Rudder to a nightly version, plugins are not upgraded added
Updated by Vincent MEMBRÉ 10 months ago
- Target version changed from 7.3.13 to 7.3.14
Updated by Vincent MEMBRÉ 8 months ago
- Target version changed from 7.3.14 to 7.3.15
- Priority changed from 100 to 98
Updated by Alexis Mousset 8 months ago
- Status changed from New to Rejected
Fixed in the new 8.1 implementation, and we probably won't fix it in previous versions.
Actions