Actions
Bug #19868
closed
Rudder package should accept plugins with same minor version, not just patch version
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Plugins integration
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
In 7.0 we want to ensure a better compability for rudder plugins with rudder server, so we enforced that rudder plugin version should exactly be the same. But in some cases, you can't update plugin directly, especially when Rudder is not connected to Rudder repositories.
So we will loosen the constraint on this and make it acceptable that we accept plugins with the same minor, there is a lot of change that they are compatible, but we also want to be able to warn and show the user that the plugin should be upgraded
Updated by Vincent MEMBRÉ about 3 years ago
- Status changed from New to In progress
Updated by Vincent MEMBRÉ about 3 years ago
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/3853
Updated by Vincent MEMBRÉ about 3 years ago
- Status changed from In progress to Pending release
Applied in changeset rudder|cfe44bb1c6906efacf516dc8bc95a18d1e97f2bb.
Updated by Vincent MEMBRÉ about 3 years ago
This bug has been fixed in Rudder 7.0.0~beta1 which was released today.
Updated by Vincent MEMBRÉ about 3 years ago
- Status changed from Pending release to Released
Updated by Félix DALLIDET about 3 years ago
- Related to Bug #20098: Rudder patch upgrade fails on plugin upgrade added
Actions