Add policy switch for location reporting and decode all policies in device_policy_cache.

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 94 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: 141
+#   For your editing convenience: highest ID currently used: 143
 #
 # 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 2194 matching lines @@
       'device_only': True,
       'features': {'dynamic_refresh': True},
       'example_value': False,
       'id': 121,
       'caption': '''Report device boot mode''',
       'desc': '''Report the state of the device's dev switch at boot.
 
       If the policy is not set, or set to false, the state of the dev switch will not be reported.''',
     },
     {
+      'name': 'ReportDeviceLocation',
+      'type': 'main',
+      'supported_on': ['chrome_os:20-'],
+      'device_only': True,
+      'features': {'dynamic_refresh': True},
+      'future': True,
+      'example_value': False,
+      'id': 143,
+      'caption': '''Report device location''',
+      'desc': '''Report the geographic location of the device.
+
+      If the policy is not set, or set to false, the location will not be reported.''',
+    },
+    {
       'name': 'DeviceUserWhitelist',
       'type': 'list',
       'supported_on': ['chrome_os:12-'],
       'device_only': True,
       'features': {'dynamic_refresh': True},
       'example_value': [ 'madmax@managedchrome.com' ],
       'id': 122,
       'caption': '''Login user white list''',
       'desc': '''Defines the list of users that are allowed to login to the device. Entries are of the form <ph name="USER_WHITELIST_ENTRY_FORMAT">user@domain</ph>, such as <ph name="USER_WHITELIST_ENTRY_EXAMPLE">madmax@managedchrome.com</ph>. To allow arbitrary users on a domain, use entries of the form <ph name="USER_WHITELIST_ENTRY_WILDCARD">*@domain</ph>.
 
@@ skipping 203 matching lines @@
       'device_only': True,
       'features': {'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': 'DeviceTargetVersionPrefix',
+      'type': 'string',
+      'supported_on': ['chrome_os:19-'],
+      'device_only': True,
+      'features': {'dynamic_refresh': True},
+      'example_value': '1412.',
+      'id': 142,
+      'caption': '''Target Auto Update Version''',
+      'desc': '''Sets a target version for Auto Updates.
+
+      Specifies the prefix of the prefix of a target version <ph name="PRODUCT_OS_NAME">$2<ex>Google Chrome OS</ex></ph> should update to. If the device is running a version that's before the specified prefix, it will update to the latest version with the given prefix. If the device is already on a later version, there is no effect (i.e. no downgrades are performed) and the device will remain on the current version. The prefix format works component-wise as is demonstrated in the following example:

[Joao da Silva, 2012/03/30 15:43:53]

s/the prefix of the prefix of/the prefix of/

+
+      "" (or not configured): update to latest version available.
+      1412.: update to any minor version of 1412 (e.g. 1412.24.34 or 1412.60.2)
+      1412.2.: update to any minor version of 1412.2 (e.g. 1412.2.34 or 1412.2.2)
+      1412.24.34: update to this specific version only

[Joao da Silva, 2012/03/30 15:43:53]

Put these examples within quotes too, it was a bit confusing when reading this.

+      '''
+    },
+    {
       'name': 'BackgroundModeEnabled',
       'type': 'main',
       'supported_on': ['chrome.win:19-', 'chrome.linux:19-'],
       'features': {
         'dynamic_refresh': True,
         'can_be_recommended': True,
       },
       'example_value': True,
       'id': 138,
       'caption': '''Continue running background apps when <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> is closed''',
@@ skipping 132 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': 'Recommended',
     },
   },
   'placeholders': [],
 }