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..1c3d1449de5739cb6475caa6b3747a7f18b6ca40 100644
--- a/chrome/browser/chromeos/arc/arc_util.h
+++ b/chrome/browser/chromeos/arc/arc_util.h
@@ -112,6 +112,18 @@ 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 the
+// flag --need-arc-migration-policy-check is missing or if the device is

[bartfab (slow), 2017/06/13 09:56:01]

Nit: Let's say "not set" instead of "missing." "Missing" sounds like something
is wrong.

[igorcov, 2017/06/16 11:13:04]

Done.

+// 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 a policy update won't change the return value after that until the
+// next Chrome restart.
+bool IsArcMigrationAllowed();
+
+// For testing IsArcMigrationAllowed, the global flags have to be reset before
+// every test.
+void ResetArcMigrationAllowedForTesting();
+
 }  // namespace arc
 
 #endif  // CHROME_BROWSER_CHROMEOS_ARC_ARC_UTIL_H_