Bug #12331
closed
rudder-pkg must disable plugin during major version Rudder update
Added by François ARMAND over 6 years ago.
Updated over 6 years ago.
Category:
Plugins integration
Description
Plugins are linked to Rudder major version API, and so they won't work after a major upgrade, even perhaps breaking things in a subtile way. So during a major version upgrade, we should disable all plugins, warn the user, and let the user install new versions (in one go once #12330 is done).
- Translation missing: en.field_tag_list set to Blocking 4.3
I'm setting that one as "blocking 4.3" even if it targets 4.2 because we must have it around the time that we release 4.3.
- Target version changed from 4.1.11 to 4.1.12
- Target version changed from 4.1.12 to 4.1.13
- Target version changed from 4.1.13 to 411
- Target version changed from 411 to 4.1.13
- Target version changed from 4.1.13 to 4.1.14
- Status changed from New to In progress
- Assignee set to François ARMAND
- 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-packages/pull/1610
- Status changed from Pending technical review to Pending release
- Target version changed from 4.1.14 to 4.1.13
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.13, 4.2.7 and 4.3.3 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by