migration for adding can_manage_optouts boolean

praekeltfoundation · Nov 12, 2013 · 0cef350 · 0cef350
1 parent b5ec968
commit 0cef350
Show file tree

Hide file tree

Showing 2 changed files with 20 additions and 1 deletion.
diff --git a/go/vumitools/account/migrations.py b/go/vumitools/account/migrations.py
@@ -54,3 +54,22 @@ def migrate_from_2(self, mdata):
         mdata.set_value('$VERSION', 3)
 
         return mdata
+
+    def migrate_from_3(self, mdata):
+        """
+        Add the can_manage_optouts boolean and default it to ``False``
+        """
+
+        # Copy stuff that hasn't changed between versions
+        mdata.copy_values(
+            'username', 'created_at', 'msisdn', 'confirm_start_conversation',
+            'tags', 'event_handler_config', 'routing_table')
+        mdata.copy_indexes('tagpools_bin', 'applications_bin')
+
+        # set the default `can_manage_optouts` value
+        mdata.set_value('can_manage_optouts', False)
+
+        # increment version counter
+        mdata.set_value('$VERSION', 4)
+
+        return mdata
diff --git a/go/vumitools/account/models.py b/go/vumitools/account/models.py
@@ -29,7 +29,7 @@ class UserAppPermission(Model):
 class UserAccount(Model):
     """A user account."""
 
-    VERSION = 3
+    VERSION = 4
     MIGRATOR = UserAccountMigrator
 
     # key is uuid