Policy implementation for encryptfs to ext4 migration strategy

chrome/browser/chromeos/arc/arc_util.h

Index: chrome/browser/chromeos/arc/arc_util.h
diff --git a/chrome/browser/chromeos/arc/arc_util.h b/chrome/browser/chromeos/arc/arc_util.h
index affd485b31b8546bc0e81891aa9e73b2d119761a..3272e33bd0459727f5b12fe135070b9c9e7d1b54 100644
--- a/chrome/browser/chromeos/arc/arc_util.h
+++ b/chrome/browser/chromeos/arc/arc_util.h
@@ -112,6 +112,17 @@ void UpdateArcFileSystemCompatibilityPrefIfNeeded(
     const base::FilePath& profile_path,
     const base::Closure& callback);
 
+// Returns if the migration from ecryptfs to ext4 is allowed. It is true if it
+// is known that the device is consumer owned, or if the device policy is
+// present and has the value |kAllowMigration|. The response is cached the first
+// time the function is used, and the policy update won't change the return
+// value after that.
+bool IsMigrationAllowed();

[hidehiko, 2017/06/09 09:40:39]

nit: could you rename to IsArcMigrationAllowed() for consistency?

[igorcov, 2017/06/09 12:55:11]

Done.

+
+// For testing IsMigrationAllowed, the global flags have to be reset before
+// every test.
+void ResetGlobalDataForTesting();

[hidehiko, 2017/06/09 09:40:39]

nit: maybe ResetArcMigrationAllowedForTesting() ?

[igorcov, 2017/06/09 12:55:11]

Done.

+
 }  // namespace arc
 
 #endif  // CHROME_BROWSER_CHROMEOS_ARC_ARC_UTIL_H_