[ChromeOS Flex] Add device policy for sending hw data

This adds a new device policy for managed ChromeOS Flex devices to
control whether detailed hardware component data can collected for
product improvement purposes. We'd like the administrator to be very
clear on what the data will be used for, and not piggy-back on other
policies that allow data collection intended for customer use.

This is Flex-only, sending hardware data, for product improvement.
Device policies should start with "Device", according to a comment in
src/chromium/src/components/policy/tools/syntax_check_policy_template_json.py
Boolean policies end with "Enabled" by convention? So our policy name:
`DeviceFlexHwDataForProductImprovementEnabled`.

Although docs/enterprise/add_new_policy.md says we need to add a
preference and register it in Local State, etc. that doesn't appear to
be necessary for Device policies.

Tested by copying the chrome_device_policy.proto to a cros_sdk, and
building libbrillo (with added accessors) against it, then using the new
accessors to check value.

Change-Id: I49282724a216cf36a09b784f174d0f4c9d589c43
Bug: b:299148409
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4908296
Reviewed-by: Roland Bock <rbock@google.com>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Commit-Queue: Ted Brandston <tbrandston@google.com>
Auto-Submit: Ted Brandston <tbrandston@google.com>
Cr-Commit-Position: refs/heads/main@{#1211486}
8 files changed
tree: 131858ead929947064d45130302cd8218c64e528
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.