Actions
User story #20261
closed
Add a warning in plugin page if a version mismatches rudder patch one
Effort required:
Name check:
To do
Fix check:
To do
Regression:
Description
We put effort to have all plugins published with rudder patch version to avoid API change.
We (of course) tolerate a different patch version (because most of the time, it just works), but we need to at least warn in plugin page that it is not the correct one.
=> add a warning message for each plugin in incorrect version
Files
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 7.0.0~rc1 to 7.0.0~rc2
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 7.0.0~rc2 to 7.0.0~rc3
Updated by François ARMAND almost 3 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND almost 3 years ago
Actually, we lose rudder version during plugin build refactoring, and so we are not able to compare on it.
We need to add "main-build.conf" in plugin jar, and read it to get the rudder version.
Updated by François ARMAND almost 3 years ago
- Related to Bug #20514: Copy main-build.conf into plugin jar added
Updated by François ARMAND almost 3 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/4085
Updated by François ARMAND almost 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|1522f18abeb045993d95477f8dbc9e3a04b4a4c6.
Updated by François ARMAND almost 3 years ago
Applied in changeset rudder|3680c03a186d59d26985a4b319e59d7f326b369b.
Updated by Vincent MEMBRÉ almost 3 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.0.0~rc3 which was released today.
Actions