Rudder

Changes in the configuration file are as follows:

$ git diff branches/rudder/2.3 master rudder-web/src/main/resources/configuration.properties
diff --git a/rudder-web/src/main/resources/configuration.properties b/rudder-web/src/main/resources/configuration.properties
index 08b1087..2d95694 100644
--- a/rudder-web/src/main/resources/configuration.properties
+++ b/rudder-web/src/main/resources/configuration.properties
@@ -178,3 +178,21 @@ rudder.batch.ptlib.updateInterval=300
 # branche). 
 # You have to use the full ref path. 
 rudder.ptlib.git.refs.path=refs/heads/master
+
+#
+# Boolean, defaults to true.
+# If true, an archive of configuration rules, groups, 
+# policy instances and user policy templates is recorded
+# to the rudder.dir.gitRoot directory specified above
+# and a git commit is performed when any of these items is modified.
+# 
+rudder.autoArchiveItems=true
+
+#
+# Boolean, defaults to true.
+# If true, when a policy instance, configuration rule,
+# group, node ... is modified, promises will be automatically
+# regenerated. If false, only a manual request for deployment
+# will trigger a deployment.
+# 
+rudder.autoDeployOnModification=true

We should treat them individually in the migration script, to ensure that each property is tested individually and fixed accordingly.

Applied in changeset commit:a47919249b688eea4e581e5e9b79159fb52395f7.