Rudder

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.