User story #2347
closed
System (internal) Techniques should be automatically upgraded when Rudder is upgraded
Description
During tests for the 2.3 -> 2.4 upgrade process, we have come to the conclusion that system Techniques should be automatically upgraded.
Up until now, we always let the user handle his own Technique upgrades, in case he had made local modifications. This is still the case, but to keep Rudder running, we do need to upgrade the system Techniques. We will implement this in the rudder-upgrade script and then call the API hook to reload the Technique library.
At the same time, any configuration files that are installed by Techniques also need to be upgraded, so we will put them into the generated promises folder for the root server (/var/rudder/cfengine-community/inputs). This is because we have no other way of making sure they are updated immediately, apart from regenerating all promises, which is not acceptable as the user may have pending changes that he doesn't want to apply yet.
Updated by Jonathan CLARKE almost 13 years ago
- Target version set to 2.4.0~alpha6
Updated by Jonathan CLARKE almost 13 years ago
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:568c458d901cf918ffb8b442a0eb595a4e671649.
Updated by Nicolas PERRON
Updated by Jonathan CLARKE over 12 years ago
- Status changed from Pending technical review to 10
Updated by Jonathan CLARKE over 12 years ago
- Status changed from 10 to Released
I think that this makes sense, system techniques are special, and if the user changed them, he still has git history to get changes back.