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..b94203d33b46c324f1406e1f03db6a6679e5928e 100644
--- a/chrome/browser/chromeos/arc/arc_util.h
+++ b/chrome/browser/chromeos/arc/arc_util.h
@@ -39,6 +39,19 @@ enum FileSystemCompatibilityState : int32_t {
   // "compatible" state. Be careful in the case adding a new enum value.
 };
 
+// The state of device policy DeviceEcryptfsMigrationStrategy, that points if
+// the migration to ext4 encryption is allowed. The ext4 encryption is required
+// for ARC(N+).
+// TODO(igorcov): Remove this after migration. crbug.com/725493
+enum class ArcAvailabilityPolicyStatus {
+  // The policy value is unknown.
+  UNKNOWN = 0,
+  // ARC is disabled.
+  DISABLED = 1,
+  // ARC is available.
+  AVAILABLE = 2,
+};
+
 // Returns true if ARC is allowed to run for the given profile.
 // Otherwise, returns false, e.g. if the Profile is not for the primary user,
 // ARC is not available on the device, it is in the flow to set up managed
@@ -112,6 +125,13 @@ void UpdateArcFileSystemCompatibilityPrefIfNeeded(
     const base::FilePath& profile_path,
     const base::Closure& callback);
 
+// Getter for |arc_availability_policy_status|.
+ArcAvailabilityPolicyStatus GetArcAvailabilityPolicyStatus();

[hidehiko, 2017/06/07 12:22:20]

Can IsMigrationAllowed be usable directly?
I do not think callers do not want to take care about UNKNOWN.

[igorcov, 2017/06/08 10:42:25]

Good point, I've replaced it. Thank you.

+
+// For testing IsMigrationAllowed, the global flags have to be reset before
+// every test.
+void ResetGlobalDataForTesting();
+
 }  // namespace arc
 
 #endif  // CHROME_BROWSER_CHROMEOS_ARC_ARC_UTIL_H_