Policy implementation for encryptfs to ext4 migration strategy

chrome/browser/chromeos/login/users/chrome_user_manager_impl.cc

Index: chrome/browser/chromeos/login/users/chrome_user_manager_impl.cc
diff --git a/chrome/browser/chromeos/login/users/chrome_user_manager_impl.cc b/chrome/browser/chromeos/login/users/chrome_user_manager_impl.cc
index b3fdb4aec500b4f9b2186d9aa58cea11fb7da672..7895e5cff4d1b7b1255bdcd760233be29899ec68 100644
--- a/chrome/browser/chromeos/login/users/chrome_user_manager_impl.cc
+++ b/chrome/browser/chromeos/login/users/chrome_user_manager_impl.cc
@@ -178,6 +178,7 @@ void ChromeUserManagerImpl::RegisterPrefs(PrefRegistrySimple* registry) {
   registry->RegisterStringPref(kDeviceLocalAccountPendingDataRemoval,
                                std::string());
   registry->RegisterListPref(kReportingUsers);
+  registry->RegisterIntegerPref(prefs::kDeviceEcryptfsMigrationStrategy, 0);

[bartfab (slow), 2017/06/12 12:49:04]

Nit: You could use
enterprise_management::DeviceEcryptfsMigrationStrategyProto::UNSET as initial
value.

[igorcov, 2017/06/12 16:50:10]

Done.

 
   SupervisedUserManager::RegisterPrefs(registry);
   SessionLengthLimiter::RegisterPrefs(registry);