ChromeOS: Add p2p_enabled field to AutoUpdateSettingsProto

chrome/app/policy/policy_templates.json

 {
 # policy_templates.json - Metafile for policy templates
 #
 # The content of this file is evaluated as a Python expression.
 #
 # This file is used as input to generate the following policy templates:
 # ADM, ADMX+ADML, MCX/plist and html documentation.
 #
 # Policy templates are user interface definitions or documents about the
 # policies that can be used to configure Chrome. Each policy is a name-value
@@ skipping 99 matching lines @@
 #   templates and documentation. The policy definition list that Chrome sees
 #   will include policies marked with 'future'. If a WIP policy isn't meant to
 #   be seen by the policy providers either, the 'supported_on' key should be set
 #   to an empty list.
 #
 # IDs:
 #   Since a Protocol Buffer definition is generated from this file, unique and
 #   persistent IDs for all fields (but not for groups!) are needed. These are
 #   specified by the 'id' keys of each policy. NEVER CHANGE EXISTING IDs,
 #   because doing so would break the deployed wire format!
-#   For your editing convenience: highest ID currently used: 241
+#   For your editing convenience: highest ID currently used: 242
 #
 # Placeholders:
 #   The following placeholder strings are automatically substituted:
 #     $1 -> Google Chrome / Chromium
 #     $2 -> Google Chrome OS / Chromium OS
 #     $3 -> Google Chrome Frame / Chromium Frame
 #     $6 is reserved for doc_writer
 #
 # Device Policy:
 #   An additional flag device_only (optional, defaults to False) indicates
@@ skipping 3529 matching lines @@
         'dynamic_refresh': True,
       },
       'example_value': True,
       'id': 136,
       'caption': '''Disables Auto Update''',
       'desc': '''Disables automatic updates when set to True.
 
       <ph name="PRODUCT_OS_NAME">$2<ex>Google Chrome OS</ex></ph> devices automatically check for updates when this setting is not configured or set to False.''',
     },
     {
+      'name': 'DeviceAutoUpdateP2PEnabled',
+      'type': 'main',
+      'schema': { 'type': 'boolean' },
+      'supported_on': ['chrome_os:31-'],
+      'device_only': True,
+      'features': {
+        'dynamic_refresh': True,
+      },
+      'example_value': False,
+      'id': 242,
+      'caption': '''Auto update p2p enabled''',
+      'desc': '''Specifies whether p2p is to be used for OS update payloads. If set to True, devices will share and consume update payloads on the LAN, potentially reducing Internet bandwidth usage and congestion.''',

[Joao da Silva, 2013/09/11 18:48:00]

Please document the default behavior, and the behavior when this is set to
False. I assume that both disallow p2p updates.

[zeuthen, 2013/09/11 19:07:20]

Correct. I'm also adding "If the update payload is not available on the LAN, the
device will fall back to downloading from an update server." to be more precise.

+    },
+    {
       'name': 'DeviceTargetVersionPrefix',
       'type': 'string',
       'schema': { 'type': 'string' },
       'supported_on': ['chrome_os:19-'],
       'device_only': True,
       'features': {
         'dynamic_refresh': True,
       },
       'example_value': '1412.',
       'id': 142,
@@ skipping 1966 matching lines @@
       'desc': '''Text appended in parentheses to the policy name to indicate that it has been deprecated''',
       'text': 'deprecated',
     },
     'doc_recommended': {
       'desc': '''Text appended in parentheses next to the policies top-level container to indicate that those policies are of the Recommended level''',
       'text': 'Default Settings (users can override)',
     },
   },
   'placeholders': [],
 }