Remote fetch device status (attributes and logs) command

components/policy/proto/device_management_backend.proto

Index: components/policy/proto/device_management_backend.proto
diff --git a/components/policy/proto/device_management_backend.proto b/components/policy/proto/device_management_backend.proto
index 1bb72401d54bf0c8fc661b943de4b5911340c3d1..e220f67e73412fb6bf6ebe14820e3c342b1201f0 100644
--- a/components/policy/proto/device_management_backend.proto
+++ b/components/policy/proto/device_management_backend.proto
@@ -1061,6 +1061,9 @@ message RemoteCommand {
 
     // Set device volume.
     DEVICE_SET_VOLUME = 2;
+
+    // Force a refresh of device status (attributes).
+    DEVICE_FETCH_STATUS = 3;
   }
 
   // The command type.
@@ -1074,9 +1077,10 @@ message RemoteCommand {
   // client, defined as current_server_time - command_generated_time.
   optional int64 age_of_command = 3;
 
-  // Extra parameters for this command, expected to be a JSON string.
-  // If the command type is DEVICE_SCREENSHOT, the format of the JSON payload
-  // is: {"fileUploadUrl" : url_string}
+  // Extra parameters for this command, expected to be a JSON string. The
+  // following are the JSON payloads for their corresponding command type:
+  // DEVICE_SCREENSHOT: {"fileUploadUrl" : url_string}
+  // DEVICE_SET_VOLUME: {"volume" : 30}

[Andrew T Wilson (Slow), 2017/03/20 16:33:10]

This seems unrelated to this CL? maybe drive this comment in a separate CL?

   optional string payload = 4;
 }